From: Junio C Hamano Date: Thu, 09 Oct 2025 21:58:09 GMT Subject: Re: [PATCH] doc: warn against --committer-date-is-author-date Message-ID: In-Reply-To: <91ddb8c2-ae3a-4b13-a23b-e5cca172ee09@app.fastmail.com> "Kristoffer Haugsbakk" writes: > On Thu, Oct 9, 2025, at 16:31, Kristoffer Haugsbakk wrote: >>> We should maybe think about deprecating it for "git rebase" though as it >>> is a lot less clear that it is sensible there. If you're rebasing a >>> branch then there is a very high likely hood that the upstream committer >>> dates of the commits the branch is being rebased onto will be newer that >>> the author dates of the commits in your branch. >> >> That makes sense. If there is no use case then it should be deprecated. >> >> I could mark it as such in the next version. >> >> Anyone else have an opinion on this? >> > > By the way. I thought of adding a stderr warning when using this option > on git-rebase(1). But I don’t think I’ve seen that used in this program > before. If so, why is that? That’s more in your face than just adding it > to the documentation. > > Is it about people parsing stderr, maybe..? Standard error stream would be buried in other progress things, and it won't be seen if you are "rebase -i" interactive, in which case the first thing you see is a full-screen editor with list of instructions (where we _could_ add new warning text).