re-implementing log-for-merge from Arch

[Aaron Bentley]

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

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
> commit:
> 
> """
> 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?

I find the "bzr log" output does this well.

I actually have a bunch of bzr logs containing log-for-merge output,
because they were converted from Arch.  They are a pain in the neck,
because they're redundant.  The same log messages that appear in the
log-for-merge output appear as part of the normal bzr log output nearby.
 It just makes it harder to read.

Now, you seem concerned about seeing the log-for-merge output at commit
time, and that seems like a reasonable request, to me.  But I'd
encourage you to look at extending the 'log --long' output so that it
can show that.

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

iD8DBQFGORol0F+nu1YWqI0RAnZKAJ0XEHolGBXprjs064Ka1d+a0s7frACfU7Y2
9kYPEV5cr3XRQRd03xuTFA4=
=JiPi
-----END PGP SIGNATURE-----