[RFC][PATCH] New revision option format

[Alexander Belchenko]

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

Goffredo Baroncelli пишет:
> Hi all,
> 
> often I read on the mailing list concerns about the current bzr revision 
> option syntax. If I want specific a range of revisions, I have to use a 
> syntax like:
> 
> -r <rev1>..<rev2>
> 
> This syntax used with the branch: revision spec and/or the dotted revision 
> number can be not very easy to read.
> 
> Examples:
> 	-r branch:../bzr.dev..1.2.3.4
> 	-r 1.2.3.4..5.6.7
> 
> I wrote a little patch which introduce a new style of the revision 
> specification. The syntax is like the CVS/SVN one: the new style is based on 
> the repeat of the switch -r/--revision  in order to specify a range:
> 
> Examples:
> 
> 	-r branch:../bzr.dev -r 1.2.3.4
> 	-r 1.2.3.4 -r 5.6.7
> 
> Todate, this patch didn't pass the test "blackbox.test_aliases". This is 
> because if I alias
> 
> [ALIAS]
> c=log -r 1

You probably want to write:

c=cat -r 1

see below...

> and then I do
> 
> $ bzr c -r 2
> 
> the command abowe will be translated in
> 
> $ bzr log -r 1 -r 2

...Because 'log' accept range of revisions...

> which will raise an error (bzr cat --revision takes exactly one number) 

..Otherwise mentioning 'cat' command have no sense.


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

iD8DBQFFUuBozYr338mxwCURAh61AJ0SSPak744/KeAd++3/HoEunKAfPACdGZRo
ECIV1SLA72QRJvXdHq0zrNU=
=tegJ
-----END PGP SIGNATURE-----