[cvsnt] Commit Identifiers on branches

larsch at belunktum.dk larsch at belunktum.dk
Wed Jun 13 12:14:17 BST 2007

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.


When using commit identifiers with update/log/diff operations, aren't you supposed
to get the revision before the commit when using "@<commitid" ?

This does not seem to be the case with the initial revision on a branch:

> cvs log -r"@954466fce284a11"

date: ...; commitid: 954466fce284a11; ...

> cvs log -r"@<954466fce284a11"

revision   <- expected revision 1.2 here

Steps to reproduce:

touch file.txt
cvs add file.txt
cvs ci -m "first rev"
cvs tag -b branch1 file.txt
echo text >> file.txt
cvs ci -m "between branch"
cvs up -rbranch1 file.txt
echo text >> file.txt
cvs ci -m "commit on branch1"
cvs up -A
cvs tag -b branch2 file.txt
cvs up -rbranch2 file.txt
echo text >> file.txt
cvs ci -m "commit on branch2"
cvs log file.txt

Getting the "revision before" the revision using commitid now yields

This is with CVSNT 2.5.03 build 2260.

Thanks for any advice,

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook