It is possible. However, I urge you to NOT do it. You will likely have more problems down the line should you do so. Please let CVS keep the revisions number private and use tags to help you keep tra
Hi all Some of the files in my cvs repository have been committed many hundreds of times and we're getting close to a major release. Is it possible to increase the major number of the revision histor
I can't speak for the other developers, but I'm open to such a patch. Sounds good to me. I know, but I felt it was worth doing anyway. Just be sure to change it again in your patch. :-) I'm not promp
Another possibility could be to start a new module/repository. Then it's quite clear where the files come from, even if they only have 1.x revisions. Of course that needs some work as well, new chec
Heh, I think you misunderstood my second message. I meant that we wanted to make the change for cosmetic reasons, not that it WAS a cosmetic change. After reading on how the branches are created, I u
Use the same command but change the order of the revisions. "Take in changes made from 1.3 to 1.4" cvs up -j1.3 -j1.4 file.c "Take out changes made from 1.3 to 1.4" cvs up -j1.4 -j1.3 file.c bye Fab
Why? Deleting a revision is almost always a mistake. It's usually a much better idea to back out a change instead. That is, rather than: cvs admin -o 1.2 Unit2.pas it's usually better to do: cvs up -
Philip> Oops, wrong. You also have to change pretty much all the Philip> lines that contain just the revision number ('3.x' in your Philip> case) to 2.x, and you also have to change all the lines Ph
It's extremely rare when I completely agree with Greg. I even partially agree with the tone of the response :-) File revision control and database replication are, indeed, two different beasts. Noel
[ On Thursday, August 9, 2001 at 18:18:39 (+0200), Iwan Birrer wrote: ] No, definitely not. Use tags to mark milestones and ignore the revision numbers -- they're really just for internal use only by
No... Like Eric mentions, this subject has been discussed before - including when I tried to implement something like an SCCS 'floor' model by raising the revisions across a CVS tree. There isn't an
[ On Sunday, June 24, 2001 at 13:40:56 (+0200), Felix von Delius wrote: ] RTFM! ;-) It's all in the manual. (your quick, serious, hint is because the "cvs import" command is designed to create a vend
[ On Tuesday, December 2, 2003 at 10:47:46 (-0500), Jim.Hyslop wrote: ] I don't mean to answer for Larry, but I will put my two cents in: It's almost impossible not to "expose" the RCS-Id in a system
Well, that depends on what the developers really want. If the developers want to control the individual version numbers, then I'd agree with you. On the other hand, the developers may want to take th
The patch that Larry put into place for this in 2000-09-27 is included after my .signature. You may also find the "modules confusion?" thread of interest: http://mail.gnu.org/archive/html/info-cvs/20
It doesn't matter that you're in the group, only the owner of a file is allowed to change its permissions. What's happening is that commit is doing a checkout after the commit in order to update any
Howdy -- I posted a script on Tuesday for someone else who was asking for the same thing. I can send it to you again if you need it. (Look for cvdiff in subject)
check out cvs2cl.pl ... I just started using it last night for the PostgreSQL project releases, and was most impressed ... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.o
First ask a invoice question: How do those guys create release change report for their projects today? The project manager need remember everything or go back to track tremendous amount of cvs logs m
I just glanced through your RCS file and it looks like perhaps some revisions were deleted improperly. There used to be bugs in the 'cvs admin -o' command which may have caused something like this, o