From: Hamish McIntyre-Bhatty <cygwin@hamishmb.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Fix typo in faq-programming.xml
Date: Thu, 27 Oct 2022 14:21:29 +0100 [thread overview]
Message-ID: <2fb67d5d-0557-707b-4ee8-82e2bf90a5b8@hamishmb.com> (raw)
In-Reply-To: <Y1psWqiNnWpDSGDs@calimero.vinschen.de>
On 27/10/2022 12:32, Corinna Vinschen wrote:
> On Oct 26 14:26, Hamish McIntyre-Bhatty wrote:
>> From: Hamish McIntyre-Bhatty <contact@hamishmb.com>
>>
>> ---
>> winsup/doc/faq-programming.xml | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/winsup/doc/faq-programming.xml b/winsup/doc/faq-programming.xml
>> index c2c4004c1..7945b6b88 100644
>> --- a/winsup/doc/faq-programming.xml
>> +++ b/winsup/doc/faq-programming.xml
>> @@ -1051,7 +1051,7 @@ a Windows environment which Cygwin handles automatically.
>> <question><para>How should I port my Unix GUI to Windows?</para></question>
>> <answer>
>>
>> -<para>Like other Unix-like platforms, the Cygwin distribtion includes many of
>> +<para>Like other Unix-like platforms, the Cygwin distribution includes many of
>> the common GUI toolkits, including X11, X Athena widgets, Motif, Tk, GTK+,
>> and Qt. Many programs which rely on these toolkits will work with little, if
>> any, porting work if they are otherwise portable. However, there are a few
>> --
>> 2.25.1
> Pushed.
>
> Thanks,
> Corinna
Cheers,
Hamish
next prev parent reply other threads:[~2022-10-27 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 13:26 Hamish McIntyre-Bhatty
2022-10-27 11:32 ` Corinna Vinschen
2022-10-27 13:21 ` Hamish McIntyre-Bhatty [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-25 18:50 Hamish McIntyre-Bhatty
2022-10-26 8:13 ` Corinna Vinschen
2022-10-26 10:35 ` Hamish McIntyre-Bhatty
2022-10-26 10:36 ` Hamish McIntyre-Bhatty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2fb67d5d-0557-707b-4ee8-82e2bf90a5b8@hamishmb.com \
--to=cygwin@hamishmb.com \
--cc=cygwin-patches@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).