From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: cygwin-patches@cygwin.com
Subject: Re: [PATCH 0/5] Fix AT_EMPTY_PATH handling
Date: Wed, 26 Jul 2023 15:12:03 +0200 [thread overview]
Message-ID: <ZMEbo2OrE9dcaAmK@calimero.vinschen.de> (raw)
In-Reply-To: <c6a8b6d9-0cce-afe8-75b0-71f60b9af0af@gmx.de>
On Jul 26 11:10, Johannes Schindelin wrote:
> Hi Corinna,
>
> I had a look over the patches and they all make sense. I also tested the
> code to make sure that the `tar xf` regression I needed to be fixed is
> also addressed by this patch series.
>
> As I don't really know the customs of the Cygwin project, please feel free
> to add any Reviewed-by:, Acked-by: or whatever footers (or, if none of
> those are appropriate, I am of course totally okay with no footer at all).
>
> Thank you so much for fixing this!
> Johannes
Great, thanks for reviewing and testing!
I'll push it later today.
Thanks,
Corinna
prev parent reply other threads:[~2023-07-26 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 12:07 Corinna Vinschen
2023-07-12 12:08 ` [PATCH 1/5] Cygwin: gen_full_path_at: drop never reached code Corinna Vinschen
2023-07-12 12:08 ` [PATCH 2/5] Define _AT_NULL_PATHNAME_ALLOWED Corinna Vinschen
2023-07-12 12:08 ` [PATCH 3/5] Cygwin: use new _AT_NULL_PATHNAME_ALLOWED flag Corinna Vinschen
2023-07-12 12:08 ` [PATCH 4/5] Cygwin: Fix and streamline AT_EMPTY_PATH handling Corinna Vinschen
2023-07-12 12:08 ` [PATCH 5/5] Cygwin: add AT_EMPTY_PATH fix to release message Corinna Vinschen
2023-07-28 16:11 ` Pedro Alves
2023-07-28 19:28 ` Corinna Vinschen
2023-07-24 15:21 ` [PATCH 0/5] Fix AT_EMPTY_PATH handling Corinna Vinschen
2023-07-26 9:10 ` Johannes Schindelin
2023-07-26 13:12 ` Corinna Vinschen [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=ZMEbo2OrE9dcaAmK@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=Johannes.Schindelin@gmx.de \
--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).