Date: Sat, 28 Feb 1998 11:59:40 +0100 (CET) From: Mikael Karpberg <karpen@ocean.campus.luth.se> To: nate@mt.sri.com (Nate Williams) Cc: cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-CVSROOT@FreeBSD.ORG Subject: Re: cvs commit: CVSROOT avail Message-ID: <199802281059.LAA04433@ocean.campus.luth.se> In-Reply-To: <199802280127.SAA07845@mt.sri.com> from Nate Williams at "Feb 27, 98 06:27:15 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
According to Nate Williams: > > BTW, why do the following work differently for remote `cvs commit'? > > Is it because the cvs client is current? > > 1) all files are handled in one batch, even if they are in separate > > directories. > > Optimization to minimize the 'commit' traffic over the wire, and to > minimize the locking. Doing a 'commit-per-directory' requires more work > than the client is willing to do at this point, and leaves the locks in > place much longer. Basically for as long as I have used CVS I have missed the ability to do "real" commit messages in an easy way. That is, do something like: cvs setmessage -m "Did this in this file" file1.c cvs setmessage -m "Did that in this file" file2.c cvs setmessage -m "Did stuff here too" blipp/file3.c cvs setmessage -m "Just did some stuff here" blipp/file4.c cvs commit -m "This message added to the messages set previously for each file" (or just: cvs commit -m "" to just use the messages each file had set for it) That way you can get sane log messages on files, and still get it commited in one big sweep, to avoid problems with people checking out in the middle of your mega-commit (which you have do do file-by file now, to get the same effect with log messages). Would someone fix this for me? :-) /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802281059.LAA04433>