Allow bundles to be viewed in visualise for review purposes

[Russ Brown]

It would be nice to be able to use bzr visualise to view the individual commits of a bundle.

How this would work I'm not really sure (I'm not sufficiently up to speed on the internals of all of this yet), but I see it working like this...

Add an 'Open Bundle' option to the file menu, and also allow a bundle filename to be specified at the command line as an argument.

It might be required that viz has access to a related branch in order for the bundle to make sense, in which case it would need to be already open with history from that branch, or in a related branch when being launched with the bundle filename on the command line. In this case, the bundle's commits would be applied to the branch's history as though it had been merged.

For many extra points, it would be fantastic to be able to open up a bundle in viz direct from the email client without having to save it first, though that's probably outside of the scope of this project.

[Daniel Schierbeck (dasch)]

That would be nice indeed. I haven't played around with the Bundle format, so I can't say if it's feasible. I've also long wanted the viz to be able to open a branch from the file menu -- adding the ability to visualize bundles would be awesome indeed.

[Aaron Bentley (abentley)]

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

Daniel Schierbeck wrote:
> That would be nice indeed. I haven't played around with the Bundle
> format, so I can't say if it's feasible. I've also long wanted the viz
> to be able to open a branch from the file menu -- adding the ability to
> visualize bundles would be awesome indeed.

I don't think anyone's really talking about bundles here. I think you
mean merge directives.

At present, you must have write access to a branch that you can install
the merge directive's bundle's revisions into. So the problem is mainly
choosing the right branch for that.

When branch stacking is implemented, Bazaar can look at making merge
directives behave more like branches, and not need installation. But
the default stacking location would be the merge directive's
target_branch, which is typically a remote location.

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

iD8DBQFILehf0F+nu1YWqI0RAikcAJ9XWPYknSB7AnKHU0YhPhbqJk94NQCfaLGF
SfkXFKTKQgO8dEou9QcFfRI=
=a+mc
-----END PGP SIGNATURE-----