[cvsnt] Tag entire repository
tmh at nodomain.org
Thu Jul 22 17:16:23 BST 2004
On Thu, 22 Jul 2004 12:03:17 -0400, "keith d. zimmerman"
<lists at kdz13.net> wrote:
>Interesting. New version means above what version number? Do I have to
>enable atomicity? Are there any implications of the above?
Something >2.0.41 (43 or thereabouts I think).
>So, if I am understanding all this correctly, this is what i should do
>to make a new release. First, background. We have branches to denote
>our major releases, and in those branches we have tags to denote a minor
>release on that branch. Our major release may diverge very much from
>the HEAD branch by the time it's done. BUT sometimes we decide the
>release branch is too fscked up (especially early in the testing/release
>cycle) and just redo the whole mess from HEAD. Occasionally this will
>orphan changes in some files, but we don't really care.
>So, what I should do in this case, if I am hearing correctly is this:
>cvs rtag -F -B <branch> *
>cvs co -A -r <branch>
>whereas I am now doing
>cvs co -A -C
>and recursing 'cvs tag -l -F -B <branch>' through that tree.
>is this all correct?
I'd normally do that kind of rollback with:
cvs update -j <branch> -j HEAD
but your way should work.
More information about the cvsnt