[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem with cvs commit -r
From: |
Jim Hyslop |
Subject: |
Re: Problem with cvs commit -r |
Date: |
Wed, 28 Sep 2005 13:21:56 -0400 |
User-agent: |
Mozilla Thunderbird 1.0.6 (Windows/20050716) |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Steven W. Orr wrote:
> We *just* started using branching here. After I locked the HEAD and
> created the new dev branch, I needed to commit some code that had been
> checked out from the HEAD and wanted to be committed to the dev branch.
I think I know the answer, but just to be sure - you didn't lock the
HEAD in order to apply the tag, did you? If you did, the lock was not
necessary.
> The commit failed because the branch locker looked at the branch that
> the files came from and not what the commit -r wanted to target.
> (Internally, my commitinfo script was doing a cvs status to see what the
> value of the "Sticky Tag:" field was.)
Instead of 'commit -r branch-tag' you could try 'update -r branch-tag'
followed by a commit.
> So, the recap is that I need to know what the value of the -r option is
> on a commit command while inside the commitinfo hook.
Looking at the documentation
(http://ximbiot.com/cvs/manual/cvs-1.11.21/cvs_18.html#SEC170) it
doesn't appear that the -r option is passed to the commitinfo script.
Would the cvs_acls script help here?
- --
Jim
-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.0.2 (Build 2424)
iQA/AwUBQzrRNS3Q8g8MicPjEQJ2AACghl+8BCSDTrtQVOBTFuR2lTz/Of8AoNl/
UQz3u7kiEZnPfhhEWEZAgPyQ
=FrKJ
-----END PGP SIGNATURE-----