You can commit to a specific revision with this command cvs commit -r rev file However, as you increase your experience with CVS, you should really abandon version numbers as a method of keeping trac
Exactly. When you update to (or checkout) a particular revision, you can't commit because there's no place (in general) to put the new revision. For example, if you have 1.1 and 1.2 already exists, y
Hi! I haven't read the full "Open Source Development with CVS" but there is a rather short and (in my opinion) clear explanation in the Cederqvist manual (chapter 4.2 "Versions, revisions and release
The NFS problem is *not* a locking problem, but actual interoperability problems between different vendors' implementations of NFS. The typical symptom is blocks of NULs in the file in lieu of real d
Hi, I've experience a couple of corrupted RCS files resulting in 'invalid change text errors'. I've looked around the web and in this archive. I've not really seen good reasons as to why it happens,
Doing similar here, I get tack:/tmp$ grep /Seyon.c/ seyon1/CVS/Entries /Seyon.c/1.36/Wed Jun 7 23:44:30 2006// tack:/tmp$ cvs-1.12.13 -q up seyon1 RCS file: /home/cvs/seyon/Seyon.c,v retrieving revis
I'm running these tests on an i386 Linux machine running Debian sarge, using binaries I've configured and compiled directly from the standard upstream tarballs for 1.12.9 and 1.12.13. I am in fact th
Hi, I have a problem with a DB2 bind file in our repository. I can check out the head revision (1.5) and the branch (1.4.0.2). If I try to check out any previous version (like 1.1) I get the error "c
I don't think you've considered all the funny cases that come into play when deleting/undeleting/branching files. Historically, the file is moved to the attic to hide it from subsequent checkouts on
While it is true that the same algorithms are used for two purposes (computing RCS deltas and presenting differences to users), what's really happening is that the diff program just happens to be in
If one wants to tag the latest on a branch, why should one have to create a workarea to do it? I have perl baseline script that automates tagging, one of the options is tagging the latest on a given
Commit uses two-phase locking principles, which means it locks everything it needs, does the processing, then unlocks. Larry's change removes twophase locking from rtag, which means that rtag can be
A quick question in the context of the question below Would it be a safe workaround to use something like -D"10 minutes ago " and assume that something currently being checked in will not be in the t
In any case, branch/timestamp pairs correctly identify the versions to be tagged. If the user specifies no branch, assume the trunk. If the user specifies no timestamp, assume the moment the command
[ On Monday, October 7, 2002 at 12:39:29 (-0400), Larry Jones wrote: ] This part I sort of agree with, though strictly to say such a thing you'd have to force them to never tag against the head of a
Why do you care what the file's revision number is? Revision numbers are for internal use only. -Larry Jones Any game without push-ups, hits, burns or noogies is a sissy game. -- Calvin
Hi All, I'm using WinCVS 1.3.7.1 against a linux cvs-1.10.7-7. I'm trying to set up a repository with two consecutive releases of source code. The problem I have is that I can't commit a edited file
point taken. but then what is the use of having a hierchal rev number if tags are what one should use? wouldn't cvs just use an incrementing number ie 1,2,3,4 instead of 1.0.1,1.0.2,etc.. -shane
The right answer is to stop thinking about the rev number and just apply a tag when you want something you can refer to. Leave the revision numbers to CVS.