RFC: Possibility to re-edit last commit message
robertc at robertcollins.net
Mon Jan 29 16:12:30 GMT 2007
On Mon, 2007-01-29 at 11:08 -0500, Aaron Bentley wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> John Arbash Meinel wrote:
> > I always thought of this as a "bzr recommit" command.
> > Definitely, I wouldn't want one that just rewrote the revision entry's
> > message field. It would need to create a new commit.
> I think "bzr recommit" may not indicate clearly enough that recommitting
> removes the last-revision.
> One way to prevent this from becoming problematic would be to mark the
> last-revision as a merge, because tools would be able to treat the new
> last-revision as effectively equal to the old last-revision.
> The downside is that marking it as a merge would make the old, undesired
> log message appear in long-format logs, which probably defeats the purpose.
OTOH, a commit which claims to supersede its second parent could tell
log to hide the second parent.
i.e. a revision property of 'supercedes: old-revision-id'.
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20070130/3051feb4/attachment.pgp
More information about the bazaar