bundle -r should be consistent with diff
Bug #57664 reported by
Martin Pool
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Invalid
|
Undecided
|
Unassigned |
Bug Description
"bzr bundle" produces what is basically an enhanced diff. One would tend to expect the commands work similarly, but they're quite different in how they handle -r.
'bzr diff -r -3' means "diff the third-last revision against the working tree"
'bzr bundle -r -3' means "give a bundle from the remembered parent branch up to revision -3".
To post a comment you must log in.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin Pool wrote:
> Public bug reported:
>
> "bzr bundle" produces what is basically an enhanced diff. One would
> tend to expect the commands work similarly, but they're quite different
> in how they handle -r.
On the other hand, they have very different purposes. 'diff' is
typically used to remind yourself of the changes you have made, while
you're working.
'bundle' is used to present your committed changes to the world in a
form that can be merged directly. Following 'diff' behaviour would
typically produce bundles that couldn't be merged directly, because they
would lack necessary ancestor revisions.
That was my rationale for making 'bundle' different from 'diff'.
Aaron enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://
iD8DBQFE7xto0F+ nu1YWqI0RAsU2AJ 9VW0n5ezkLGAbA+ sVBdNdilSYiagCc Clt7 Q//JqJXSow=
e3nNo2H4VzqQ+
=gdty
-----END PGP SIGNATURE-----