rfc: remove "revision specs"

[Matthieu Moy]

Martin Pool <martinpool at gmail.com> writes:

> Previous versions of bzr allowed for "revision specifiers" to occur
> within a path, e.g.
>
>   ./bzr.dev/@1040

One thing I like with the baz revision identifier, like
foo at bar/proj--main--0--patch-42 is that you can easily recognize that
it's a revision identifier. You can recognize it visually, or program
software to regexp-match it. For example, Xtla now creates
mouse-sensitive buttons in my emails when it recognizes such pattern.

It can do that if the mail says

  Please look at foo at bar/proj--main--0--patch-42

but off course not if the mail says

  Please see patch-42 that I've just commited in foo at bar/proj--main--0


I'd like revision identifiers to be regexp-matchable in bzr too,
although I'm not sure how it's possible to do it.
bzr:///home/foo/bar/,rev=1040  could be nice, but OTOH,
bzr://http://www.site.com/my/bzr/branch/,rev=1040  looks really ughly.

In brief, revision specifiers within a path are a necessary condition
to have easily recognizable bzr revision specifiers, but it's not
sufficient. Or perhaps forget about this all if this is too complex
for too little benefit ...

-- 
Matthieu