RFC: Possibility to re-edit last commit message

[John Arbash Meinel]

Michael Ellerman wrote:
> On 1/29/07, Jari Aalto <jari.aalto at cante.net> wrote:
>>
>> It happens that when the message is committed, it wasn't quite the way
>> it supposed to be:
>>
>>     * formatting
>>     * grammar
>>     * typos
>>     * missing information
>>     * something come up, that fot to be mentioned
>>
>> In case of local branches (not checked out one), it would be nice if the
>> message could be re-edited
>>
>>     bzr ci --re-edit
>>
>> And that would bring up the editor just like last time. After exiting
>> the editor, that message would be updated (no files updated)
> 
> But if someone has pulled the branch in the meantime, and you change
> the message without creating a new commit, you're in a world of pain.
> So just uncommit, edit the message and recommit. It might be nice to
> have a plugin that does it for you though.
> 
> cheers
> 
> 

I always thought of this as a "bzr recommit" command. Which could do 2
things.

I actually tend to leave the commit message alone, but actually add in
another file, or find something small that I forgot to include. So I
would like to "bzr recommit" to uncommit and commit with the same
message, but the new tree state.

I realize it may be a little tricky to know whether you are wanting to
edit the commit message, or the tree state, and you may want to recommit
the message after you have modified the tree. So a flag for something like:

bzr recommit --no-tree-changes

For the message, if we spawned an editor with the old message, I could
always just accept it. But the command should support '-m' like the
current commit command does.

At least, that has been my thoughts.

Definitely, I wouldn't want one that just rewrote the revision entry's
message field. It would need to create a new commit.

John
=:->