RE: CVS Not Updating to latest revision...

[Fisher, Allen]

Larry--

Thanks for the response. I took a look, and it appears that none of the
files are branched. The logs looked pretty normal. In fact, this portion
of the repo has not been branched at all...

I did a CVS status on one of the directories that was a problem and I'd
see things like

File: blah.htm    Status: up-to-date

Working Revision: 1.4
Repository Revision: 1.1
Sticky Tag:
Stickty Options:

Existing tags:
(Long list of tags, although many tags for automated builds don't show
up)

The two red flags are the working revision and the fact that not all the
tags show up.

 

> -----Original Message-----
> From: Larry Jones [mailto:address@hidden 
> Sent: Thursday, December 21, 2006 10:28 AM
> To: Fisher, Allen
> Cc: CVS Mailing List
> Subject: Re: CVS Not Updating to latest revision...
> 
> Fisher, Allen writes:
> > 
> > Hope I'm posting this to the correct place. We've placed our
> > documentation under CVS control, and I'm having a bit of 
> trouble getting
> > the latest revision. I've checked to make sure that no 
> sticky tags are
> > set, and I've tried checking out to a different sandbox on 
> my machine. I
> > always get revision 1.1, even though there have been 
> numerous revisions
> > since then.
> 
> It sounds like your document editor has been committing to a branch
> rather than the trunk.  Do "cvs log" on one of the files that should
> have multiple revisions and see what it says.
> 
> -Larry Jones
> 
> My brain is trying to kill me. -- Calvin
>