Peter,
If you want good CVS comments (comments that actually apply to the changes in the file), then changes must be committed on the per file (or per logical change) base. If someone has to commit 5 unrelated changes, or each file needs different checkin messages for each, then they must be commited seperately. And if you do a cvs update during that period, the build will fail. There is no way around that, multiple commits can't be done atomicly in CVS. I'm guilty of the same problem of doing a cvs update; build.sh, and when it breaks, complaining about it (Scott S. can testify to that). But, when you see something like that, you need to wait an hour or so, before complaining, to let the developer form good checkin messages. Without those, we have no way of determining what happened when. -David On Wed, 05 Dec 2001, Peter Fagerlund wrote: > MAN - let me spell it out then ! > > -heh > > Do not check in -if it do not build ! ... > > Clear ... > > /peter_f > > on 1-12-05 01.22, Jason Dillon at [EMAIL PROTECTED] wrote: > > > I totally don't understand any of the emails you send. I don't mean to be > > offensive, I just don't get it. > > > > --jason > > > > > > On Wed, 5 Dec 2001, Peter Fagerlund wrote: > > > >> on 1-12-04 21.52, Julian Gosnell at [EMAIL PROTECTED] wrote: > >> > >>> I updated my RH tree 1/2 an hour ago, made clen and rebuilt - no problems. > >> > >> Yes that is the way - build - no probs -> but there seems to be some slack > >> here -and that is counterproductive inbeetwen - i build now - hurray ... > >> > >> IMNSHO > >> > >> /peter_f > >> > >> *wordthatarelonger*thenthisisnogood = clear ! > >> *counterproductive* > >> > > > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
