From: Patrick Steinhardt <ps@pks.im>
To: Christian Reich <Zottelbart@t-online.de>
Cc: git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Johannes Sixt <j6t@kdbg.org>
Subject: Re: [PATCH v2] reftable: ignore file-in-use errors when unlink(3p) fails on Windows
Date: Fri, 14 Mar 2025 16:00:28 +0100 [thread overview]
Message-ID: <Z9REjHgrhzUzWoqJ@pks.im> (raw)
In-Reply-To: <de954c02-8711-43e9-8f4c-259718034497@t-online.de>
On Fri, Mar 14, 2025 at 03:18:55PM +0100, Christian Reich wrote:
> Greetings,
>
> the patch didn't find the way in next git version.
>
> But there is a change in git for windows, which prevents multiple asks the
> same questions:
>
> https://github.com/git-for-windows/git/commit/dba1473162b4319a0a2c7f74ab48ed4a826f7ac7
>
> The other option to prevent the asks, is to set GIT_ASK_YESNO but the sleeps
> slow down the process.
The patch is still blocked because [1] hasn't landed yet. Once it does I
expect the patch to be merged. But yes, this will not be part of Git
v2.49, but of the next release.
Patrick
[1]: <20250127-pks-reftable-drop-git-compat-util-v1-0-6e280a564877@pks.im>
next prev parent reply other threads:[~2025-03-14 15:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 5:41 [PATCH] reftable: ignore file-in-use errors when unlink(3p) fails on Windows Patrick Steinhardt
2025-01-25 8:19 ` Johannes Sixt
2025-01-25 8:32 ` Patrick Steinhardt
2025-01-25 14:28 ` Johannes Sixt
2025-01-27 7:48 ` Patrick Steinhardt
2025-01-28 6:52 ` Johannes Sixt
2025-01-28 7:17 ` Patrick Steinhardt
2025-01-29 7:40 ` Johannes Sixt
2025-01-25 8:45 ` Christian Reich
2025-01-27 7:58 ` Patrick Steinhardt
2025-01-26 1:41 ` Junio C Hamano
2025-01-27 7:57 ` Patrick Steinhardt
2025-02-06 7:53 ` [PATCH v2] " Patrick Steinhardt
2025-03-14 14:18 ` Christian Reich
2025-03-14 15:00 ` Patrick Steinhardt [this message]
2025-03-15 23:17 ` Johannes Schindelin
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=Z9REjHgrhzUzWoqJ@pks.im \
--to=ps@pks.im \
--cc=Johannes.Schindelin@gmx.de \
--cc=Zottelbart@t-online.de \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
/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 NNTP newsgroup(s).