Junio C Hamano <gitster@xxxxxxxxx> writes:
> Johannes Altmanninger <aclopte@xxxxxxxxx> writes:
>
>>> > !f() { GIT_SEQUENCE_EDITOR=true git rebase -i --autosquash "$@"; };f
>>>
>>> These are very good and useful features indeed, and they are examples of
>>> batch processing that is very handy for automation, but lacks
>>> interactivity. What I rather have in mind is being able to put all the
>>> messages /simultaneously/ into my favorite text editor and edit them
>>> more or less freely till I'm satisfied, then "commit" the overall result
>>> by passing it back to git. Essentially "git rebase -i" on steroids.
>>
>> git-revise is a third-party tool that can do this
>>
>> https://git-revise.readthedocs.io/en/latest/
>>
>> For example, "git revise -ie" allows you to edit all commit messages in
>> @{u}..HEAD in a single buffer.
>
> I only looked at its description but the UI the tool does it with
> looks quite obvious and intuitive. From its source, the "merge"
> operation does not seem to handle merging a side branch that renamed
> files, but that should be OK most of the time, I presume.
>From the docs:
No merge commits may occur between the target commit and HEAD, as
rewriting them is not supported.
>
> Nice.
Yeah, it is!
-- Sergey
