thread names in urls (Re: Creating a branch other than master using bzr-git)

[Stephen J. Turnbull]

Martin Pool writes:

 > I was thinking about perhaps ".../branch/+thread".  "+" has the
 > advantage of being visually a metacharacter, but not one that has a
 > strong meaning in either the unix or windows shell, or in http.

You crack me up!  I have a private convention (with git, where
branches generally are "local") of doing builds in subdirectories, and
I distinguish the build directories for different branches by
prefixing "+" to the branch name.  I have "+*" in my user gitignore,
of course.

I'm not complaining or suggesting that *my* usage is a reason not to
use "+", but I wonder how many other people have hit on that
convention (I bet a lot of Arch-ers and ex-Arch-ers use it, for
example).

 > It's used by convention as a short escape for space characters in
 > filenames, but if I recall correctly (and we should check) this is
 > not mandated or assumed, just a convention that servers use in
 > mapping urls to the filesystem.

Actually, that would be the worse case because people using multiple
servers might find the rules changing on them from location to
location.  I also suspect that that convention would be implemented on
the browser side rather than the server side.

Firefox 3 doesn't seem to implement it.