From owner-cvs-all Sat Feb 28 10:55:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06612 for cvs-all-outgoing; Sat, 28 Feb 1998 10:55:02 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06607 for ; Sat, 28 Feb 1998 10:55:00 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA08177; Sat, 28 Feb 1998 11:54:56 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA10848; Sat, 28 Feb 1998 11:54:54 -0700 Date: Sat, 28 Feb 1998 11:54:54 -0700 Message-Id: <199802281854.LAA10848@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mikael Karpberg Cc: nate@mt.sri.com (Nate Williams), cvs-committers@FreeBSD.ORG Subject: Re: cvs commit: CVSROOT avail In-Reply-To: <199802281059.LAA04433@ocean.campus.luth.se> References: <199802280127.SAA07845@mt.sri.com> <199802281059.LAA04433@ocean.campus.luth.se> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk > > > 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? :-) No. If you need to do alot of commits, do them one-by-one. The danger of someone committing something in the middle is small, so single-commits are not difficult to do nor that big of a problem. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message