Changing a commit message
Stefan Monnier
monnier at iro.umontreal.ca
Thu May 15 21:49:32 BST 2008
> As I have already written (in my response to Raul's message), I don't
> want to make decentralized Bazaar workflows allow any commit messages
> changes. I understand the fact it would lead to a great mess with
> propagation of such changes.
I completely disagree: you can of course come up with contrived
situations where changing commit massages generated heaps of frivolous
and frustrating conflicts, but that's no reason not provide the feature,
whether you use a centralized workflow or not.
In practice modifying commit messages is something that's only used
occasionally, so the risk of major merge trouble is completely blow out
of proportions.
The only problem with providing the feature are technical: what should
the UI feature look like, where should the changes be stored, how should
conflicts be shown to the user.
I'm a deep believer in the Arch way of keeping as many things as
possible as "plain files", so I'd keep the "commit amendments" as
a normal file (like .bzrignore, tho I'd rather store them both somewhere
under .bzr). The main downsize of this is that it makes it more
difficult to change the representation used.
Stefan
More information about the bazaar
mailing list