bzr bundle > file

[Aaron Bentley]

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

Gustavo Niemeyer wrote:
> Hello Aaron,
> 
>> If you're saying that specifying revisions for inclusion in the bundle
>> is a valuable feature, then it would be bad to only support it via a
>> deprecated command.  If it's actually worth supporting, we should make
>> "send" support it, right?
> 
> Most of the times when I've used the bundle command, it was with
> the -r parameter.  Whenever I'd send a "diff" to someone to explain
> an idea over a review, for instance, I send a bundle which may be
> used to integrate in the branch being reviewed.

For that purpose, send's -r will Do The Right Thing.

Say the target branch is totally empty.

You have revisions 1, 2, 3.  You do

bzr send -r 2..3

The bundle will contain revisions 1, 2, 3.  The preview patch will be
the same as "diff -r 2..3".  When it is merged, the effect will be the
same as "merge -r 2..3".

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

iD8DBQFGuxdG0F+nu1YWqI0RArxlAJ4q5DKo2Ye30JBL+4RavTH77FogcgCeJGoK
S9NV5AbctwyWcBA5plcFRSc=
=B9z+
-----END PGP SIGNATURE-----