Received: (at submit) by bugs.debian.org; 19 Nov 1996 17:54:29 +0000 Received: (qmail 3229 invoked from network); 19 Nov 1996 17:54:29 -0000 Received: from cartridge.i-connect.net (qmailr@206.139.73.12) by master.debian.org with SMTP; 19 Nov 1996 17:54:29 -0000 Received: (qmail 30892 invoked from network); 19 Nov 1996 17:13:49 -0000 Received: from gatekeeper.verisim.com (206.51.251.97) by cartridge.i-connect.net with SMTP; 19 Nov 1996 17:13:47 -0000 Received: from callandor ([192.168.1.3]) by gatekeeper.verisim.com with smtp id m0vPtX3-000H4zC (Debian Smail-3.2 1996-Jul-4 #3); Tue, 19 Nov 1996 12:00:21 -0500 (EST) Sender: bcwhite Message-ID: <3291E392.615A0C6B@verisim.com> Date: Tue, 19 Nov 1996 11:42:58 -0500 From: "Brian C. White" Organization: Verisim, Inc. http://www.verisim.com/ X-Mailer: Mozilla 3.01 (X11; I; Linux 2.0.22 i486) MIME-Version: 1.0 To: Debian Bugs Subject: cvs won't accept -r on new commit Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Package: cvs Version: 1.8.1-1 When committing a new file, CVS looks through all existing files and chooses the highest major revision number as the default starting point. In my opinion, this is a mis-feature since the first revision of any given file should be, by default, 1.0. The bug is that this behavion cannot be overridden. Giving the "-r" flag to CVS causes RCS to fail. Adding the new file goes normally: callandor:~/build/coordinator> cvs add -m "Routines to parse/generate vCalendar Files" vcal.h cvs add: scheduling file `vcal.h' for addition cvs add: use 'cvs commit' to add this file permanently If I try to specify the full revision: callandor:~/build/coordinator> cvs commit -r 1.0 -m "Routines to parse/generate vCalendar Files" vcal.h RCS file: /var/cvs/coordinator/Attic/vcal.h,v done rcs: invalid symbol `1.0' rcs aborted cvs commit: could not stub branch 1.0 for /var/cvs/coordinator/Attic/vcal.h,v Not specifying the revision code gives: callandor:~/build/coordinator> cvs commit -m "Routines to parse/generate vCalendar Files" vcal.h Checking in vcal.h; /var/cvs/coordinator/vcal.h,v <-- vcal.h new revision: 3.1; previous revision: 1.1 done If I start over and just specify the major revision, it will work then: callandor:~/build/coordinator> cvs commit -r 1 -m "Routines to parse/generate vCalendar Files" vcal.h RCS file: /var/cvs/coordinator/Attic/vcal.h,v done Checking in vcal.h; /var/cvs/coordinator/Attic/vcal.h,v <-- vcal.h new revision: 1.2; previous revision: 1.1 done I don't understand why this was put in the "Attic", though. It is still accessible as though it was not in the Attic. Note: This behavior is the same between v1.8 and v1.9. Brian ( bcwhite@verisim.com ) ------------------------------------------------------------------------------- the difference between theory and practice is less in theory than in practice