David Leskovac writes:
Okay. So, just to be clear, this is actually a 3-step process:
1. Checkout branch:
cvs co -r branchname module
2. Rename from sandbox:
cd to root of module in sandbox
cvs admin -n newname:oldname
3. Delete original tag name sandbox:
cd to root of
David Leskovac writes:
If the cvs admin -n command renames branches why the need to delete
the original branch name? What happens if you don't delete the original name?
admin -n doesn't rename the branch, it just creates a new name for it.
If you don't delete the old name, you can use either
David Leskovac writes:
Would this work for each branch to be renamed?:
cvs rtag -b -r original_branch_name new_branch_name module
No, that creates a new branch off of the existing branch rather than
renaming the existing branch. You need to use admin -n instead.
-Larry Jones
Kicking dust
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
working
Would this work for each branch to be renamed?:
cvs rtag -b -r original_branch_name new_branch_name module
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
David Leskovac writes:
Okay. So rather than the 2-step process I mentioned in my original post
where I would create a new branch from the original branch then delete
the original branch, there is a way to simply rename the existing branch
with a cvs admin -n command? I looked at the syntax
David Leskovac wrote:
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 original_branch_name
David Leskovac writes:
Okay. So, just to be clear, this is actually a 3-step process:
1. Checkout branch:
cvs co -r branchname module
2. Rename from sandbox:
cd to root of module in sandbox
cvs admin -n newname:oldname
3. Delete original tag name sandbox:
cd to root of module
Could one use:
cvs rtag -r oldname newname .
Larry Jones [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Yes, use cvs admin -n to create the new tag pointing to the same...
___
Info-cvs mailing list
[EMAIL PROTECTED]
Dennis W. Bulgrien writes:
Could one use:
cvs rtag -r oldname newname .
No. That will create a revision tag pointing to the most recent
revision on the branch rather than creating a new name for the branch
itself. Likewise, adding a -b to create branch tag rather than a
revision tag will
You can create a synonym of a branch using:
cvs admin -nNEWBRANCH:OLDBRANCH
and then you can remove OLDBRANCH.
-- Strong suggestion is to back up your repository, I've only tested this -
I've never used it in anger. There's no rolling back from mistakes.
-Original Message-
From:
Hi Boris,
i assumbe you mean rename the branch tag?
cut from the Cederquvist...:
When we say rename a tag, we mean to make a different name point
to the same revisions as the old tag. For example, one may have
misspelled the tag name and want to correct it (hopefully before others
are
Jim Harkins [EMAIL PROTECTED] writes:
Like an idiot I came up with a branch name that is not only too long and
unwieldy, but it no longer accurately reflects it's contents. Is there a
good way to rename a branch?
As long as you can prevent other people from accessing the repository
while
13 matches
Mail list logo
