[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index


From: Flanakin Michael C Ctr HQ OSSG/OMR <Michael.Flanakin.Ctr_at_Gunter.Af.Mil>
Date: 2005-12-01 22:58:12 CET

I'm sure shelving isn't a new concept, but this is the first time I've
heard about it. Are there any planned additions of a similar type of
capability in Subversion? For those that don't know, shelving allows you
to make modifications and do a partial commit. Check outs and updates
don't get the shelved content. A separate command (i.e. unshelve) gets
the shelved mods. Then, additional mods can be made and committed when
the changes are complete.
I see shelving as a useful feature because there are times where someone
might go on vacation and want to commit what they have without breaking
anything. Then, if someone else knows what changes need to happen, they
can unshelve and finish the changes.
Now, my first thoughts are that this can be simulated by simply creating
a "shelves" directory alongside the branches, tags, and trunk
directories. Then, someone could theoretically branch to shelve code.
These mods would ultimately be merged back into trunk like branches are.
The only real question I have about this method is: will it suffice?
This is the first time I've seen shelving, so I'm not sure if there's
something else that'd be useful.
Does anyone have any experience with shelving code (with or without
Svn)? I'd love to hear about anyone's experiences to see if the branch
method works as expected and/or if there are any caveats that may hinder
its implementation.
Michael Flanakin
Received on Thu Dec 1 23:12:24 2005

This is an archived mail posted to the Subversion Users mailing list.