From: Kristoffer Haugsbakk <code@khaugsbakk.name>
Date: Wed, 19 Nov 2025 16:27:15 GMT
Subject: Re: [PATCH] doc: warn against --committer-date-is-author-date
Message-ID: <da44a9ce-6e04-43c3-be1a-5db640c20e98@app.fastmail.com>
In-Reply-To: <xmqqbjm695p4.fsf@gitster.g>

On Thu, Oct 16, 2025, at 18:23, Junio C Hamano wrote:
> Johannes Sixt <j6t@kdbg.org> writes:
>>[snip]
>> I do not like the latter. If you do not like the former, I wouldn't mind
>> not adding the sentence. The warning should be sufficient.
>
> But stepping back a bit, if we truly want to discourage the use of
> it, perhaps we should officially deprecate and schedule it for
> removal?  If we are *not* brave enough to back such a move, then
> perhaps we ourselves are not yet convinced that this should be
> discouraged?
>
> My preference is to stop at describing, in WARNING or NOTES, what
> the use case that triggered the addition of this option was and
> declaring that the use case does not make any sense (your "who would
> apply the same series twice on the same base?  just keep the result
> on a branch and reuse" would be fine), but without saying "Do not
> use this option".  In other words, the message is "We'd give a long
> rope that we do not think is very useful, but it is up to you to get
> yourself tangled in it".

I agree with just warning.