[cvsnt] Commit Identifiers on branches

[Arthur Barrett]

Lars,

Any chance you can retest that with 2.5.04 testing build - or failing
that at least 2.5.03.2382 (which is the stable build)?

Thanks,


Arthur

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of larsch at belunktum.dk
Sent: 13 June 2007 21:14
To: cvsnt at cvsnt.org
Subject: [cvsnt] Commit Identifiers on branches


Hello,

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"

...
revision 1.2.2.1
date: ...; commitid: 954466fce284a11; ...
...

> cvs log -r"@<954466fce284a11"

...
revision 1.1.2.1   <- 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 1.2.2.1 using commitid now
yields revision 1.1.2.1.

This is with CVSNT 2.5.03 build 2260.

Thanks for any advice,
Lars

_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt