"Jim.Hyslop" wrote: > > Swaroop George wrote: <SNIP> > > > > - Is there anyway of alternate versioning and making it much more > > simple, but still maintaining the history to an extent. > I'm almost certain your branching and versioning strategy can be simplified. > It's been my experience that when people create such a complex branch > structure sit down and analyze what they really need (along with an expert > who truly understands branching) the branch and merge process becomes _much_ > simpler. <SNIP> Along those lines you (or your to be branching expert) should probably take a look at Brad Appleton's "Assembling Configuration Management Environments" pages[1] (and books). He has a section specifically on branching techniques and reasoning[2], which I have found useful in the past. I thought I had seen some user feed back in some sections where individuals noted how they had used the pattern under various version control tools, and how it worked for them.
[1] http://www.cmcrossroads.com/bradapp/acme/ [2] http://www.cmcrossroads.com/bradapp/acme/#Branching http://www.cmcrossroads.com/bradapp/acme/branching/ -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
