Charvi Mendiratta <charvi077@xxxxxxxxx> writes:
> For end-users "-m" or "-F" will make it easier to prepare an "amend!"
> commit. Because using the "-m" reduces the cost of opening an editor
> to prepare "amend!" commit and it can be done with command line only.
Hmph. That is not very convicing to me. The user is motivated
enough to fix a wrong commit log message and replace it with an
improved one by using the "--fixup:amend" feature---why would that
improved message can sufficiently be written with just an "-m
message", which by definition would be much less capable of
preparing a well-thought-out message than with an editor?
Yes, with "-m", you can add some short string easily at the end of
the existing commit message without opening an editor. But I am
trying to see why it is a good thing to be able to do so in the
first place. It is very easy to make typoes while doing so and it
would be hard to fix these typoes, exactly because you are doing so
without being in an editor. And the whole point of --fixup=amend is
about improving the message (as opposed to --fixup that is to record
the contents that have already been improved in the index).
This is why I kept asking what the use case would look like. I am
trying to find out if you have a good end-user story in mind that we
can use in the documentation to sell the feature to end-users, but I
am not seeing one.
Is the combination of "--fixup=amend" and "-m <msg>" meant to be
used primarily "to leave a note to myself" when the user runs
--fixup=amend:<commit>, to just record the points to be elaborated
when the message is written for real much later? E.g.
... hack hack hack ...
... good stopping point, but cannot afford time to write
... a good log message now
$ git commit --fixup=amend:HEAD~2 -m 'talk about X, Y and Z' -a
... hack hack hack ...
... possibly doing something entirely different ...
... finally comes back to finish cleaning up the branch for real ...
$ git rebase --autosquash -i origin
And one of the insn created in the todo sheet would be amend!, whose
commit message has the message taken from the original HEAD~2 PLUS the
reminder to the user that s/he needs to talk about X, Y and Z? And
the user at that point writes more comprehensive message about these
three things?
That is a made-up example of what "appending some short strings
possibly full of typoes without having to open an editor" could be
useful for. I am not sure if it is truly useful, or if it is just a
hand wavy excuse not to mark -m/-F incompatible with --fixup=amend
without a real merit [*].
Side note: one reason why I do not find it realistic is that it
is unlikely that the user would use --fixup=amend to slurp in
the original log message when recording "good stopping point,
but cannot afford time" fixup. "--squash HEAD~2 -m <msg>" would
be much faster to record the "note to myself" reminder, and when
the user finally comes back to clean things up, the amount of
work to edit the original's message while looking at the "note
to myself" appended at the end would not be any different in
either workflow.
In any case, that was the kind of answer(s) I was looking for when I
asked "what is this good for?" question.
Thanks.
