From: Junio C Hamano <gitster@pobox.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: "Torsten Bögershausen" <tboegi@web.de>, git@vger.kernel.org
Subject: Re: t4216-log-bloom.sh broken ?
Date: Thu, 02 May 2024 12:55:44 -0700 [thread overview]
Message-ID: <xmqq7cgcdm4f.fsf@gitster.g> (raw)
In-Reply-To: <20240502192622.GA1841@szeder.dev> ("SZEDER Gábor"'s message of "Thu, 2 May 2024 21:26:22 +0200")
SZEDER Gábor <szeder.dev@gmail.com> writes:
>> Yes, different mac, different MacOs, different $PATH probably.
>> ...
>
> 'mv' in macOS doesn't conform to POSIX, and asks for confirmation when
> the destination exists (is read-only?) even without '-i' and even when
> its stdin is not a terminal, which it won't get as its stdin in our
> test suite is redirected from /dev/null.
>
> This is a recurring issue, see e.g.:
>
> https://public-inbox.org/git/20180616143513.10086-1-szeder.dev@gmail.com/
> c20d4d702f (t1450: use "mv -f" within loose object directory, 2017-01-24)
>
> 'mv -f' did the trick in the past.
Hmph, while that is a good data point to explain why this one fails,
it is a very unsatisfactory workaround, compared to a world where we
do not have to worry about such a broken mv (perhaps by noticing a
broken macOS /bin/mv and automatically doing mv () { mv -f "$@" }
for them).
I am curious what other differences Torsten will find out between
good macs and bad ones. Perhaps we can narrow down the bad apples?
next prev parent reply other threads:[~2024-05-02 19:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 17:12 [ANNOUNCE] Git v2.45.0 Junio C Hamano
2024-05-01 17:39 ` rsbecker
2024-05-02 5:56 ` t4216-log-bloom.sh broken ? Torsten Bögershausen
2024-05-02 16:06 ` Junio C Hamano
2024-05-02 18:59 ` Torsten Bögershausen
2024-05-02 19:26 ` SZEDER Gábor
2024-05-02 19:55 ` Junio C Hamano [this message]
2024-05-02 20:05 ` Junio C Hamano
2024-05-02 20:15 ` Junio C Hamano
2024-05-02 20:51 ` Torsten Bögershausen
2024-05-02 21:20 ` Junio C Hamano
2024-05-02 16:26 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq7cgcdm4f.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=szeder.dev@gmail.com \
--cc=tboegi@web.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).