From: Lidong Yan <yldhome2d2@gmail.com>
Date: Sun, 19 Oct 2025 14:31:27 GMT
Subject: Re: [PATCH] diff: stop output garbled message in dry run mode
Message-ID: <DEF57576-E0E5-4F09-B7E7-CE1B8753F088@gmail.com>
In-Reply-To: <xmqqa51ow6xu.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:
> 
> Yup, that matches my expectation more closely, which is
> 
> * We'll do the "send to /dev/null as we used to do before the
>   dry-run thing" on the 'maint' front, which will be merged up to
>   'master' and above.
> 
> * We'll queue "here are fixes to the recently introduced dry-run
>   code" (without the /dev/null thing mixed in), and cook that in
>   the usual 'seen' down to 'next' down to 'master' route.
> 
> In a distant future, we may consider removing the /dev/null thing
> once the dry-run code path proves to be stable and robust.
> 
> Thanks.

I am not sure what should I do. Should I make a new patch which
only contains “fixes to the recently introduced dry-run code” without
Peff’s code in it? Or Junio would do that for me?

Thanks,
Lidong