re-implementing log-for-merge from Arch
John Arbash Meinel
john at arbash-meinel.com
Wed May 2 22:31:51 BST 2007
-----BEGIN PGP SIGNED MESSAGE-----
Dan Lipsitt wrote:
> What would it take to implement something like the log-for-merge
> command present in tla and baz? I found it to be a useful feature. For
> those of you not familiar with Bazaar 1 and Arch, it automatically
> creates a log message like this, which the user can then edit before
> Summary: Merged from dan at harvard.edu--myarchive (patch 6-7)
> Keywords: merge
> Patches applied:
> * dan at harvard.edu--myarchive/myproject--mainline--1.1--patch-6
> changes in low-level parallization code
> * dan at harvard.edu--myarchive/myproject--mainline--1.1--patch-7
> new parallelized version
> Or is there already a good way to get this info from bzr?
> If this is a worthwhile project and it isn't too complicated, I may
> try to implement it as a plugin. However, I'm not sure where to begin.
Well, 'bzr status' gives a pretty good summary. It just doesn't include
the revision ids.
It probably wouldn't take a lot. But considering "bzr log --long"
already shows all of that (as a properly nested merge), do you really
need to write it again in the new commit message?
It seems a little redundant.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the bazaar