RFC: Possibility to re-edit last commit message

[Jari Aalto]

John Arbash Meinel <john at arbash-meinel.com> writes:
>> Thank you for the epxplanation. What about if we did simply this:
>> 
>>   ci --message-only
>> 
>> And be able to provide new message. No files would change, just the
>> message would be versioned and increase the revision id N+1. Would
>> that be possible?
>
> bzr commit -m "new message" --unchanged
>
> Which allows you to commit even if there are no changes in the working
> tree. It would still commit any real changes, though. But yes, you can do:

This is the problem. I would just need a new message right after the
old one; with version N+1, if that's the feasible solution. No actual
file commits whatsoever even if they had changed.

That would suffice now when we consider that it's impossible to actually
change the last committed message (due to distributed nature).

> But it sounded more like you wanted to change an existing revision,
> removing it from history and replacing it with something new. And to me,
> that would be 'bzr recommit'.

Not removing, keeping it there, but stacked -- where the last one would
only be visible. But if I understood correct there would have been
problems.

Once more:

    r1      -- bunch of files ci'd in       
            -- with message
    
    <hack, change files, view the previous log .. Ooops!>
    <I would really need to correct the log, it talks about bug 1234, and
    <it should refer to bug 1235>

    bzr commit -m "new message" --unchanged --message-only

    r2      -- no file changes
            -- new message 

Would that be possible?

Jari