Junio C Hamano wrote: > Jonathan Nieder <jrnieder@xxxxxxxxx> writes: >> Lukas Gross wrote: >>> I had intended to stage commits but forgot to do so. Git responded >>> with a normal commit creation message, so I pushed to the remote to >>> begin a CI build. When the build failed for the same reason, I >>> realized [...] >> $ git commit --amend --no-edit >> [detached HEAD 33a3db8805] Git 2.23-rc1 >> Author: Junio C Hamano <gitster@xxxxxxxxx> >> Date: Fri Aug 2 13:12:24 2019 -0700 >> 2 files changed, 2 insertions(+), 1 deletion(-) >> $ >> >> Some non-judgemental descriptive output like >> >> $ git commit --amend --no-edit >> No changes. >> $ >> >> would address this case, without bothering people who are doing it >> intentionally. So I think there's room for a simple improvement here. > > I do that to refresh the committer timestamp. I do, too. The proposal is, paraphrasing, $ git commit --amend --no-edit Ah, I see that you want me to refresh the committer timestamp. Done, as requested. $ In other words: [...] > I am not > yet convinced that "--amend --no-edit will become a no-op" is the > final solution we want. Not this. Hoping that clarifies, Jonathan
