Problem with cvs commit -r

[Steven W. Orr]

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.

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.)

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.

Anyone?

TIA

--
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang dot net