Previewing merge directive contents?

[John Arbash Meinel]

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

On 1/27/2011 8:26 AM, Alexander Belchenko wrote:
>>
> 
> That's true but it does not help much: you still need separate branch to
> merge directive and without qlog it's not so cool to explore revisions
> with "status -v". I can imagine
> 
> bzr log /path/to/merge/directive
> 
> will produce real log to the user.
> 

I believe there is already a bug/feature request for us to treat a merge
directive as just another branch. Effectively they are similar to
stacked branches, only the stacked on target is whatever branch you have
locally.

However, it would be a fair rework of the internals to get that to work.
Possibly worthwhile, but not quite at the level that we've focused on it.

That would certainly allow "bzr log path/to/merge-directive", etc.

John
=:->

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

iEYEARECAAYFAk1BldoACgkQJdeBCYSNAAPYsgCghMdglSXvaMIpFoJm8QFY/tHP
+IYAnRDEDSW3CW9UjLJz3MnXKiq2HoNc
=8EKs
-----END PGP SIGNATURE-----