Flanakin Michael C Ctr HQ OSSG/OMR wrote:
> The main reason I like shelving is because I've been in numerous
> situations where code changes need to be passed from one person to the
> next or, due to project needs, you're required to stop working one task
> to start another. Personally, I'd like to have a place to save these
> changes without committing them.
> This is of course based on my VC
> methodology - only commit completed, compilable code (say that 5xs
> fast). Of course, the files could be saved locally, but then they risk
> being accidentally deleted. I'd rather have all these changes in one
> place, rather than risking rework. This way, any developer can pick up
> where another left off, if need be.
fair enough, though i disagree. a private branch can contain anything in
my world, even un-compilable code
> I also don't completely agree with your opinion that it's a backup. I do
> see what you mean, but it depends on how the shelves are used. For
> instance, a team may have the C4 philosophy I use, but a developer may
> want to commit their changes more frequently for a large code change.
> Shelves can directly support that.
i don't understand this, do you say a shelve supports committing, [ie.
it has a a list of entries in its log history ?] if so, what exactly is
the difference from a branch ?
> Whether you call them shelves or private branches, I could care less.
> It's the capability that I think would be important to document.
true ;)
./allan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 5 20:48:43 2005