On Thu, 1 Apr 2004, Donald Sharp (sharpd) wrote: > -----Original Message----- > From: Hugh Sasse Staff Elec Eng [mailto:[EMAIL PROTECTED] [...] > > Thank you for the responses... > On Wed, 31 Mar 2004, Paul Sander wrote: > > > --- Forwarded mail from sharpd(.--.-.)cisco.com > > > > Create your own private branch to do work on. When you want to save > > work, commit the code. When you are done, merge the changes down. > > The book "Open Source Development with CVS" says that you should keep > few branches active at any one time. I'm wondering if there are > penalties (apart from storage costs) when many contributors create their > own branches? > > ---> Yes there are significant penalties with cvs in creating too many > branches. > ---> I wouldn't worry about this if you are in a small shop( under 25 > developers ) > ---> though. I'm pretty sure this has been discussed ad infinitum here > though, > ---> do a quick search to find this information :)
OK, I'll do that, I couldn't think of a narrow enough pattern not to get spadefuls of info from google, etc! > > Also, doesn't having a separate branch for your own development make > doing an update in between edits more difficult? > > ---> Creating your own branch, definately increases the process that you > work with. > ---> It's easy though, just more process. I'll probably have to play with that a bit to get a feel for what is happening. I think I'll get hold of CVSGraph http://www.akhphd.au.dk/~bertho/cvsgraph/ to help me out with this. > > > > > Other possibilities include implementing a backup system that takes > > hourly snapshots.... > > Yes, but it would be less flexible than SCCS, I think... > > ---> Just trying to give suggestions ;) OK, thanks. > > ---> odnald Thank you, Hugh _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
