Re: Git Feature Request (Commit Message editing directly from interactive rebase control file)

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 23, 2020, 23:33 UTC
Message-ID: <xmqqh7oc5c96.fsf@gitster.c.googlers.com>
In-Reply-To: <CAM0jFOfvNFva98PNjO33HW3Y4+L1SufvEHQYzwGLHgOkfhmUDQ@mail.gmail.com>

Mike McLean <stixmclean@googlemail.com> writes:

Show 12 quoted lines

> I initially raised this as a FR with my git UI of choice, and was told
> that it was actually something that git itself would need to do ...
> and that the standard way to raise Feature Requests was to email this
> list.
>
> Apologies if that's not actually what I should be doing - please let
> me know if this is not an intended use.
>
> =-=-=-=-=-=-=-=-=-=
> When you do an interactive rebase, you are presented with a file
> listing all the commit hashes, their current message, and the
> command/operation to perform.

Each commit is shown only with their title, but does not show the full message, exactly because the text is merely there to help the user identify which commits are being shown and manipulated.

> ...
> So can we allow the user to (optionally) set the new message directly
> in that file?

I suspect that such a "feature" would encourage people to use a single liner commit log message, that is only the title, so that they do not have to worry about the real log message in the body. And it does not particularly feel a good behaviour that we'd want to encourage. So, I dunno.