RFC: Possibility to re-edit last commit message

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jari Aalto wrote:
> John Arbash Meinel <john at arbash-meinel.com> writes:
>> Regardless, this seemingly simple change actually has a lot of
>> long-reaching ramifications in a distributed system. So I will second
>> Larz's suggestions for: "Don't worry about it too much."
> 
> 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?
> 
> It sounds simple solution, because the messages do sometimes need
> serious updates (like referring to wrong bug numbers, wrong urls,
> other mistakes that affect the project in general)
> 
> Jari
> 

You can always do:

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:

$ cd branch
$ bzr commit -m "nothing has changed" --unchanged
$ bzr commit -m "nothing has changed" --unchanged
$ bzr commit -m "nothing has changed" --unchanged
$ bzr commit -m "nothing has changed" --unchanged
$ bzr commit -m "nothing has changed" --unchanged


And 'bzr log' will show you 5 revisions with the message "nothing has
changed".

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'.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFvmrcJdeBCYSNAAMRAmjEAJwKwYsyN2YfWzBhJjk6kcCeO5lAigCfamXT
NuZzypxhYP0skE1xg9sHvew=
=QuwW
-----END PGP SIGNATURE-----