[Top][All Lists]

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

Re: Undesired Sticky Tags With cvs update

From: Bob Bowen
Subject: Re: Undesired Sticky Tags With cvs update
Date: Mon, 25 Feb 2002 14:51:37 -0600

Eric Siegerman wrote:
> On Mon, Feb 25, 2002 at 06:54:17PM +0000, Chuck Taylor wrote:
> > I discovered last week that if I run
> >
> >     cvs update -f -r <branch_tag>
> >
> > in a working directory, then files that don't have <branch_tag>
> > defined are checked out from the main trunk, as the -f option directs.
> > However, CVS still applies the <branch_tag> sticky tag to these files,
> > so subsequent cvs status commands result in errors on files that don't
> > have the tag:
> >
> >     cvs status: <file> is no longer in the repository
> >     ...
> >     File:  <file>    Status: Entry Invalid
> IMO that's a bug.  CVS shouldn't be able to put its own data
> structures into a state that it considers invalid.
> That said, why are you only tagging some of the files?  Just tag
> everything; then it won't be a problem.
> And using -f to override that, though of course
> it shouldn't put CVS's data structures into an invalid state,
> also shouldn't be expected to make up for the initial "garbage in".

Then what is the purpose of the -f option? I've also run into this situation and
as best as I can tell, using -f never gives you a viable result. You do get the
desired versions, but as far as CVS is concerned, the workarea is unusable. Few
cvs commands will work.

Does anyone know why -f works this way?

Bob Bowen  address@hidden  Process Engineering  (952)876-4635

reply via email to

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