rfc: remove "revision specs"

Robert Collins robertc at robertcollins.net
Tue Aug 30 05:43:15 BST 2005

On Tue, 2005-08-30 at 14:22 +1000, Martin Pool wrote:
> Previous versions of bzr allowed for "revision specifiers" to occur
> within a path, e.g.
>   ./bzr.dev/@1040
> User feedback has been fairly clear that people would prefer just to
> use the -r options they're accustomed to from cvs and svn.  Not all
> commands handle them.  So I propose to just delete support for
> revision specifiers.
> In previous versions it was necessary to use a revision specifier for
> the merge command, but not anymore.

Theres an interesting thing with PQM here. PQM current specifies
revisions for arch branches as part of the specification. I.e.
"merge me at example.org/baz--0--patch-34 thelove at canonical.com/baz--0"

I'd like some similar mechanism to provide an exact revision to PQM for
bzr. The @ annotation is crufty imo because its not following the RFC
for url parameterisation.

however, something like './bzr.dev,rev=1040' is std66 conformant for url
path element parameterisation. I think that that is not great for
command line ui, but it would be nice to retain the unambiguous
single-string facility.


GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050830/2c8b62cc/attachment.pgp 

More information about the bazaar mailing list