Using branches

[Charles Pope]

>>>
	If it's a branch that is common for a lot of developers, you can put  
it up as a different tree.  That's essentially what you do in, for  
example, subversion or perforce.  You get a particular path if you  
want the main branch, and a different path if you want a different  
path.  You can push to one or the other, and merge between them.
<<<

Thanks for your detailed reply. I am thinking about the branches you would
have for major releases, which would be shared. In CVSNT we have branches
which roughly follow a naming convention, down which we maintain releases
(but then we don't really use lightweight branches).

So when you talk about a different tree, this might be a separate clone of
the repository representing a particular release (perhaps cloned at the
point of release). But in the end the code all originally derives from the
same source point so you can move fixes between repositories.

By the way, does the repository have to sit in a parent folder of the source
files? The only way I found around this was to use the folder link
functionality in windows.

Thanks

Charles
-- 
View this message in context: http://www.nabble.com/Using-branches-tf4070369.html#a11602335
Sent from the Mercurial mailing list archive at Nabble.com.