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 email@example.com.
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 126.96.36.199 date: ...; commitid: 954466fce284a11; ... ... > cvs log -r"@<954466fce284a11" ... revision 188.8.131.52 <- 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 184.108.40.206 using commitid now yields revision 220.127.116.11. 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 cvsnt downloads at march-hare.com https://www.march-hare.com/cvspro/en.asp#downcvs @CVSNT on Twitter CVSNT on Facebook