[RFC][PATCH] New revision option format

[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

and then I do

$ bzr c -r 2

the command abowe will be translated in

$ bzr log -r 1 -r 2

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

Comments are welcome.
Ciao
Goffredo
-- 
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack at inwind.it>
Key fingerprint = CE3C 7E01 6782 30A3 5B87  87C0 BB86 505C 6B2A CFF9
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rev.diff
Type: text/x-diff
Size: 5028 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20061108/e9bdf1ae/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20061108/e9bdf1ae/attachment.pgp