Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
> -----Original Message----- > From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On > Behalf Of Gerhard Fiedler > Sent: Friday, April 06, 2007 12:16 PM > To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > Subject: Re: [cvsnt] Branch creation takes a long time > > Rick Martin wrote: > > > Don't want to steal the OP thread, but what would you consider to be > a LOT > > fo branches? > > I work for a manufactoring company and due to the software design we > do an > > official release every two weeks to the factory floor. I'm creating > a > > branch for each of these and then creating a tag if we need to > release a > > bug fix on the build branch. This creates a fair number of branches > and > > tags. Too many? > > I'm not sure I understand your procedure correctly, but couldn't you > tag > these official releases, and only branch this tag later if you > actually > need to do some bug fixing? Assuming that fixing bugs in an official > release is the exception rather than the rule, this would cut down > quite a > bit on the number of branches. > > Gerhard FYI, the current maintainers of the CVS source tree (from which CVSNT is derived) consider "20" branches to be a large number. Our source tree has over 2000 branches, which is what lead me to create the patch improving branch time. Before the patch our branches took 112 minutes, after the patch they take around 10-15 minutes.... -Kelly