From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2025, #08; Thu, 23)
Date: Fri, 24 Oct 2025 09:06:04 -0700 [thread overview]
Message-ID: <xmqqsef8p9n7.fsf@gitster.g> (raw)
In-Reply-To: <20251024154719.GA1779502@coredump.intra.peff.net> (Jeff King's message of "Fri, 24 Oct 2025 11:47:19 -0400")
Jeff King <peff@peff.net> writes:
> On Thu, Oct 23, 2025 at 04:36:01PM -0700, Junio C Hamano wrote:
>
>> * jc/diff-from-contents-fix (2025-10-22) 1 commit
>> (merged to 'next' on 2025-10-23 at fae07d2113)
>> + diff: make sure the other caller of diff_flush_patch_quietly() is silent
>> (this branch is used by ly/diff-name-only-with-diff-from-content; uses jk/diff-from-contents-fix.)
>>
>> The code to squelch output from "git diff -w --name-status"
>> etc. for paths that "git diff -w -p" would have stayed silent
>> leaked output from dry-run patch generation, which has been
>> corrected.
>>
>> Will merge to 'master'.
>> source: <xmqqy0p4wcac.fsf@gitster.g>
>
> OK, looks like you picked up the fix from the last round of discussion.
> Good. Is this destined for 'maint'? My patch fixed the regression from
> v2.51.1 with "--quiet", but I think there is still one for "-w --raw",
> etc.
The plan is to merge "j?/diff-from-contents-fix" down to 'maint';
any other changes that tweak dry-run are to be done 'next' down to
'master' but not to 'maint' as a longer term "true fix".
next prev parent reply other threads:[~2025-10-24 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 23:36 What's cooking in git.git (Oct 2025, #08; Thu, 23) Junio C Hamano
2025-10-24 15:47 ` Jeff King
2025-10-24 16:06 ` Junio C Hamano [this message]
2025-10-24 16:59 ` Jeff King
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=xmqqsef8p9n7.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).