From: Junio C Hamano <gitster@pobox.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>, git@vger.kernel.org
Subject: Re: t4216-log-bloom.sh broken ?
Date: Thu, 02 May 2024 14:20:54 -0700 [thread overview]
Message-ID: <xmqq4jbfdi6h.fsf@gitster.g> (raw)
In-Reply-To: <20240502205121.GB11895@tb-raspi4> ("Torsten Bögershausen"'s message of "Thu, 2 May 2024 22:51:21 +0200")
Torsten Bögershausen <tboegi@web.de> writes:
> Thanks folks for digging - the patch makes both test cases pass.
> Some official information:
>
> $ man mv
>
> on the both machines says
> [snip]
> If the destination path does not have a mode which permits writing,
> mv prompts the user for confirmation as specified for the -i option.
>
> To summarize what I have at hand right now:
> MacOs 11.7.10 fails t4216 and t5318, both pass under MacOs 13.6.6
>
> But why doesn't `mv` not hang then ?
It is a sensible choice for the command to assume a "safer" no and
continuing rather than hanging, so that part is understandable.
So presumably 13.6.6 has a working "mv" but their "man mv" is not
updated to how the command actually works?
In any case, let me declare victory and queue the patch I sent
earlier.
Thanks.
next prev parent reply other threads:[~2024-05-02 21:21 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq4jbfdi6h.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.