info-cvs
[Top][All Lists]
Advanced

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

Re: cvs update doesn't!


From: Kaz Kylheku
Subject: Re: cvs update doesn't!
Date: Fri, 04 Jan 2002 18:40:44 GMT
User-agent: slrn/0.9.6.3 (Linux)

In article <address@hidden>, Ian Dall wrote:
>CVS does not seem to work properly for me. Since the problem
>is pretty basic, I assume it is my naivety, which is the problem
>rather than a bug. I'd appreciate if someone can enlighten me.

Your problem looks suspiciously like you blew the repository away
since August and then imported afresh in November, leaving any
working copies in an indeterminate state.

>RCS file: /usr/local/cvs-rep/netbsd/src/usr.bin/make/parse.c,v
>Working file: parse.c
>head: 1.1
>branch: 1.1.1
>locks: strict
>access list:
>symbolic names:
>       current-2002-01-04: 1.1.1.1
>       current-2001-11-25: 1.1.1.1
>       src: 1.1.1
>keyword substitution: kv
>total revisions: 2;    selected revisions: 2
>description:
>----------------------------
>revision 1.1
>date: 2001/11/25 13:24:31;  author: ian;  state: Exp;
>branches:  1.1.1;
>Initial revision
>----------------------------
>revision 1.1.1.1
>date: 2001/11/25 13:24:31;  author: ian;  state: Exp;  lines: +0 -0
>Importing distribution 2001-11-25

The evidence here all points to parse.c having been created for the
first time on November 25, 2001. There is no evidence of an August
revision. It's impossible to have an August checkout of a repository file
that didn't exist until November, unless there was a previous repository
that was clobbered.

>Ah. Looks OK to my inexpert eye. A version was imported on November 25.
>Now lets look in the local CVS directory:

In fact the *only* version was imported on November 25. The version 1.1
and 1.1.1.1 always refer to the same revision in CVS.

So to figure out how you got here, you will probably have to recall
anything you might have done between August and November.


reply via email to

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