I think it'd be best to have a separate root directory to distinguish
the concept separately. In effect, I may want to shelve 3 files, whereas
I would branch the entire repository. Or, would shelving the entire
repository be the recommended practice, in this instance?
From what I remember, shelving (or private branching) isn't discussed in
the docs. Would it be beneficial to officially accept a "shelves"
directory as a best practice and update the docs? I think it'd be nice
to publicly announce the feature so those who are new to Svn (and even
CM as a whole) can understand how it's done as well as understand the
differences between branches and shelves. In my opinion, saying that
shelves are branches is like saying that tags are branches (or
vice-versa). Technically, they are; however, conceptually they are
completely different. Again, just my opinion.
From: Paul Koning [mailto:firstname.lastname@example.org]
Sent: Thursday, December 01, 2005 5:03 PM
To: Flanakin Michael C Ctr HQ OSSG/OMR
Subject: Re: Shelving
>>>>> "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
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.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Dec 2 14:31:05 2005