>David Leskovac writes:
>>
>> Okay. So, just to be clear, this is actually a 3-step process:
>> 1. Checkout branch:
>>cvs co -r
>> 2. Rename from sandbox:
>>cd to root of module in sandbox
>>cvs admin -n newname:oldname
>> 3. De
>> Would this work for each branch to be renamed?:
>> cvs rtag -b -r
>
> No, that creates a new branch off of the existing branch rather than
> renaming the existing branch. You need to use admin -n instead.
Okay. So rather than the 2-step process I mentioned in my original post
where I would
> You still need a 2-step process, you just use admin -n to create a new
> name for the existing branch rather than using tag -b to create a new
> branch:
>
> cvs admin -n newname:oldname
> cvs tag -d oldname
>
> (Note that there's no "radmin" command so you need to have a checked out
Hi,
Sorry for the basic question but I need to implement a new branch
naming scheme & want to make sure I am doing this correctly.
To start this process, I need to rename several existing branches.
Would this work for each branch to be renamed?:
cvs rtag -b -r
cvs rtag -d
I am aware of the
> Is any one doing Continuous Integration with CVS ?
Yes. We use CruiseControl 2.2.1
-Dave
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
> It's working just as designed. :-) Variables that stay
> around "permanently" only stay that way as long as you are
> logged in. I suggest adding it to your .bashrc file in your
> home directory. UNIX/Linux process that file every time a new
> terminal session is opened and will set it autom
way to rename a file in the trunk &
retain the history of the oldfile in the newfile while keeping the
oldfile intact in the branches?
Thanks,
-Dave
-Original Message-
From: Jim.Hyslop [mailto:[EMAIL PROTECTED]
Sent: Friday, March 11, 2005 10:33 AM
To: David Leskovac; info-cvs@gnu
Hi,
Will the following commands work to rename a file in the
trunk but retain the old file name in all its branches?:
cvs co
cvs remove -f
cvs add
cvs commit -m"Renamed to "
Thanks,
-Dave
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.
> Install cvs in a different place than the version you are using.
>
> Make a script named cvs in the current location of cvs. That
> script should check the cvs commands vs. valid users. If
> everything is OK, then it should invoke the new cvs in the
> new place with the arguments passed to it.
[I sent this msg 10 days ago & noone responded. So, I'm trying again.]
Hello,
We are currently using an ancient version of CVS (1.11.1p1) on a rather old
Linux server (Red Hat 6). I intend to upgrade to CVS 1.11.19 & eventually
upgrade the Linux OS. In the course of our CVS upgrade discussion w
Hello,
We are currently using an ancient version of CVS (1.11.1p1) on a rather old
Linux server (Red Hat 6). I intend to upgrade to CVS 1.11.19 & eventually
upgrade the Linux OS. In the course of our CVS upgrade discussion we started
discussing how to increase security with regards to CVS acce
11 matches
Mail list logo