From: Jon Turney <jon.turney@dronecode.org.uk>
To: Cygwin Patches <cygwin-patches@cygwin.com>
Subject: Re: [PATCH 0/2] Fix build with w32api 10.0.0
Date: Thu, 28 Apr 2022 14:23:05 +0100 [thread overview]
Message-ID: <1d636cfc-6d0b-3ef0-38b3-9af31f423ce5@dronecode.org.uk> (raw)
In-Reply-To: <20220428092902.d7cb9331078f1e97f9fee144@nifty.ne.jp>
On 28/04/2022 01:29, Takashi Yano wrote:
> On Wed, 27 Apr 2022 11:30:44 +0200
> Corinna Vinschen wrote:
>> On Apr 12 18:32, Jon Turney via Cygwin-patches wrote:
>>> Jon Turney (2):
>>> Cygwin: Fix build with w32api 10.0.0
>>> Cygwin: Fix typo KERB_S4U_LOGON_FLAG_IDENTITY -> IDENTIFY
>> ^^^^^^^^^^^^^^^^^^^^
>> Ooooops
>>
>> LGTM, thanks,
>> Corinna
>
> Shouldn't these patches be applied also to cygwin-3_3-branch?
>
Yes, I guess so. My mistake that they weren't.
prev parent reply other threads:[~2022-04-28 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 17:32 Jon Turney
2022-04-12 17:32 ` [PATCH 1/2] Cygwin: " Jon Turney
2022-04-12 17:32 ` [PATCH 2/2] Cygwin: Fix typo KERB_S4U_LOGON_FLAG_IDENTITY -> IDENTIFY Jon Turney
2022-04-27 9:30 ` [PATCH 0/2] Fix build with w32api 10.0.0 Corinna Vinschen
2022-04-28 0:29 ` Takashi Yano
2022-04-28 13:23 ` Jon Turney [this message]
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=1d636cfc-6d0b-3ef0-38b3-9af31f423ce5@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).