Why does each developer need his or her own branch. Just pull a workspace and have the developer treat his local workspace as a branch. That way whoever commits first forces everyone else to auto-update and pull in the changes... Instead of waiting till the end.
donald On Wed, May 28, 2003 at 06:39:00PM -0300, Giovanni Giazzon wrote: > Hi all, > I'm quite new to CVS, and I'm having some difficulties to understand it's > logic. I have a project in the HEAD "section", and I've created a branch to > each developer. So they work on it, commit on it, and we are all happy, but > when comes the time to generate a new version and merge each branch, I feel > like having no gain in productivity. It's hard to merge three or more > branches since different implementations can converge in a same file. That's > the problem of work with multiple instances of a same file: if you work by > demand, you might have logical concurrence in different implementations. > But, is this right? That's the way to work with CVS? > > Regards, > Giovanni Giazzon > > > > _______________________________________________ > Info-cvs mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
