From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: Ian Turner <vectro@vectro.org>, git@vger.kernel.org
Subject: Re: Bug report: Undocumented interaction of --exit-code and --ignore-space-change for file move
Date: Mon, 23 Sep 2024 15:32:39 -0700 [thread overview]
Message-ID: <xmqqzfnyvw54.fsf@gitster.g> (raw)
In-Reply-To: <2c3472d4-ad40-4636-9840-51fa97bca02b@web.de> ("René Scharfe"'s message of "Mon, 23 Sep 2024 20:08:58 +0200")
René Scharfe <l.s.r@web.de> writes:
> 87cf96094a (diff: report copies and renames as changes in
> run_diff_cmd(), 2024-09-08) fixes it, but it's not in any release, yet.
Thanks.
It should first appear in Git 2.46.2 and would be in Git 2.47.
prev parent reply other threads:[~2024-09-23 22:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 16:29 Bug report: Undocumented interaction of --exit-code and --ignore-space-change for file move Ian Turner
2024-09-23 18:08 ` René Scharfe
2024-09-23 22:32 ` Junio C Hamano [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=xmqqzfnyvw54.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
--cc=vectro@vectro.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).