>>>>> "Flanakin" == Flanakin Michael C Ctr <Flanakin> writes:
Flanakin> I'm sure shelving isn't a new concept, but this is the
Flanakin> first time I've heard about it. ...
Flanakin> Now, my first thoughts are that this can be simulated by
Flanakin> simply creating a "shelves" directory alongside the
Flanakin> branches, tags, and trunk directories. Then, someone could
Flanakin> theoretically branch to shelve code. ...
I hadn't heard the term either. But I've heard of "private branches"
as the way to do this. That's the generally recommended way,
especially in version control systems that handle branches efficiently
(SVN, ClearCase). It's even the recommended way in version control
systems that handle branches poorly (CVS).
You could certainly make a separate top level directory if you want to
have the notion of shelving as a separate concept worthy of a name of
its own. Or you could just tell people that what they are doing is
private branches -- and have them create subdirectories under
/branches for this.
Come to think of it, I've thought of having either
/branches/private_branches or just /private_branches as a way to keep
the "big branches" namespace somewhat less cluttered.
paul
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 2 00:23:12 2005