info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emergency, always get the old revision without sticky tag.


From: Todd Denniston
Subject: Re: Emergency, always get the old revision without sticky tag.
Date: Fri, 04 Nov 2005 09:40:59 -0500

Leon Wu wrote:
> 
> Hi Everyone:
>    I have a A.cpp file, its HEAD revision is "1.18". Recently every
> time I run "cvs update" or "cvs checkout", I always get "1.17" revision
> 
> without sticky tag or date. After modified and committed this file, a
> new branch "1.17.2.1" was added to the repository, Firstly I don't
> notice, do like this for 2 times, now in the "1.17" there are 2 branch
> "1.17.2.1" and "1.17.3.1". Then "cvs update -r 1.18 A.cpp", I get the
> "1.18" revision, but the sticky tag is "1.18", after "cvs update -A" I
> get "1.17" revision again. Please help. I use wincvs 2.0.2.4(build 4).
> 

This sounds very strange. It might help us to figure it out if you could
include some information telling us more of what cvs thinks is going on,
like the output to:

#assuming *nix & bash
export FILEOFINTEREST=A.cpp
export DLASTLINE=`cvs log $FILEOFINTEREST | \
grep -n description: |awk -F: '{print $1}'`
cvs log $FILEOFINTEREST |head -$DLASTLINE
#check for dead revs
export DEADMAYBE=`cvs log $FILEOFINTEREST| \
grep -1 "state: dead"`
if [ "x$DEADMAYBE" != "x" ] 
then
  echo "we have a dead revision at ($DEADMAYBE)"
fi
#and status
cvs status $FILEOFINTEREST


-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter




reply via email to

[Prev in Thread] Current Thread [Next in Thread]