Command for "show-changeset"
aaron.bentley at utoronto.ca
Tue May 10 20:51:00 BST 2005
-----BEGIN PGP SIGNED MESSAGE-----
John A Meinel wrote:
| Erik Bågfors wrote:
|> On 5/10/05, John A Meinel <john at arbash-meinel.com> wrote:
|>> Erik Bågfors wrote:
|> I would expect -r twice to diff two revisions. I don't know why? Does
|> it work like that in other SCMs?
| Maybe. I think CVS might do something like this. However, -r111:222 is
| more consistent, I think, and having the same option given twice is
| currently an error in the bzr code.
Yes, it's like that in CVS. In most tools, when you repeat an option,
the second value overrides the first. I think that's what people
expect. However, Python's optparse also supports the CVS approach, so
it's not totally unknown.
I'd want diff to be able to diff specific revisions of specific
branches. So eventually, I'd want this to work:
bzr diff release/@192 devel/@295
So I favour the two-argument approach over the colon-separated approach.
~ But if we can support both, and it'll make people happy, let's do it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the bazaar