Looking for a way to get merge directive contents

[John Arbash Meinel]

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

Erik Bågfors wrote:
| When I run merge or pull, the directive acts like a branch "bzr pull
| <directive>".
|
| Why shouldn't I be able to run "bzr log <directive>"?
|
| /Erik
|
| Sent from my iPhone

A directive only has meaning in the context of a branch. 'log' is defined in
terms of a single branch, while 'pull' and 'merge' have 2 branches. So you have
context to understand the merge directive. (Mostly because a lot of the entries
will be deltas against existing revisions, so we can't recreate the full text
otherwise.)

That said, I believe Robert's work on stacked branches might make it a bit
easier to pretend a merge directive is just another branch with limited history.
But fundamentally you run into the problem of context. bzr doesn't generally use
the local directory as context (you can run bzr log http://foobar from any
directory).

That doesn't mean it has to be that way forever, but that is our current pattern.

John
=:->

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

iEYEARECAAYFAkhFesMACgkQJdeBCYSNAAMdmQCcDk0enRGDFlHBPnqBfNKIrRxM
4Z4AoIdj/7kI0MmpgQO+CyE6Vmb/jufJ
=aQPw
-----END PGP SIGNATURE-----