Re: [Monotone-devel] Branch naming

[Nathaniel Smith]

On Sat, Nov 15, 2003 at 11:28:17AM -0500, graydon hoare wrote:
> but it's also a scalability need of some large projects *not* to have
> a "single" root to their authority hierarchy, but rather maintain a
> separate semi-fork which supports their own needs, and only share
> *some* changes, from time to time.

What if we specify that as a matter of convention, net.venge.monotone
belongs to you, and you further delegate
net.venge.monotone.local.<reversed hostname>.<blah> to the owner of
<hostname>?  So things like net.venge.monotone.win32,
net.venge.monotone.fixes.refactor, etc. are official branches, and if
Kevin wants to do some local refactoring, he can just create
net.venge.monotone.local.com.qualitycode.refactor, and there's no
danger of accidental collision.

Con: net.venge.monotone.local.com.qualitycode.refactor is a touch
annoying to read and type.  Maybe there's a more readable way to do
this...
  net.venge.monotone-local-com.qualitycode-refactor ?
  net.venge.monotone-local:com.qualitycode-refactor ?
  net.venge.monotone-local:qualitycode.com-refactor ?

-- Nathaniel

-- 
"On arrival in my ward I was immediately served with lunch. `This is
what you ordered yesterday.' I pointed out that I had just arrived,
only to be told: `This is what your bed ordered.'"
  -- Letter to the Editor, The Times, September 2000