info-cvs
[Top][All Lists]
Advanced

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

Re: cvs co -D date problem


From: Malcolm Fernandes
Subject: Re: cvs co -D date problem
Date: Tue, 11 Dec 2001 17:54:31 -0800

Re-sending, looking for any other input/solutions.

Thanks,

Mal

Malcolm Fernandes wrote:

> Hi Rob,
>
> cvs --version
>
> Concurrent Versions System (CVS) 1.11.1p1 (client/server)
>
> Copyright (c) 1989-2001 Brian Berliner, david d `zoo' zuhn,
>                         Jeff Polk, and other authors
>
> Regards,
>
> Mal
>
> Rob Helmer wrote:
>
> > Hi Malcolm,
> >
> > Hmm, just tried to reproduce this, I get :
> >
> > cvs server: warning: test/bin/lcp.sh is not (any longer) pertinent
> >
> > This is with CVS 1.11 on Solaris. What version are you running ( "cvs
> > --version" to find out )?
> >
> > Thanks,
> > Rob Helmer
> >
> > Malcolm Fernandes wrote:
> >
> > > Hi Rob,
> > >
> > > Here is the scenario.
> > >
> > > cvs up foo.c
> > > rm foo.c
> > > cvs remove foo.c
> > > cvs ci foo.c
> > >
> > > The file gets removed from my workspace.
> > >
> > > Then,
> > > cvs co -D"`date`" foo.c
> > >
> > > The file will re-appear in your workspace.
> > >
> > > Regards,
> > >
> > > Mal
> > >
> > >
> > > Rob Helmer wrote:
> > >
> > >> Hi Malcom,
> > >>
> > >> Hmm, ok, maybe I am missing something. Can you give an example?
> > >>
> > >> Do you mean that you removed something ( for example ) yesterday,
> > >> and when you checkout using a timestamp from today, the removed file
> > >> is not removed from your workspace? Or that it is updated, but not
> > >> removed?
> > >>
> > >> I'll investigate it further if you can give me something I can
> > >> reproduce on
> > >> my end. It sounds like a bug, if anything like that is happening.
> > >>
> > >> Thanks,
> > >> Rob Helmer
> > >>
> > >> Malcolm Fernandes wrote:
> > >>
> > >> >Hi Rob,
> > >> >
> > >> >I'm not trying to pull an old snapshot of the code.   The build script
> > >> >checks out the tree based on the current timestamp using "`date`".
> > >> >This timestamp is embedded in the target load, so that developers can
> > >> >reproduce the code base, based on this timestamp.
> > >> >
> > >> >I would expect that files which were previously removed from CVS,
> > >> would NOT
> > >> >get checked out in my workspace, if I were to use the current
> > >> timestamp.
> > >> >
> > >> >Regards,
> > >> >
> > >> >Mal
> > >> >
> > >> >
> > >> >Rob Helmer wrote:
> > >> >
> > >> >>On Tue, Nov 13, 2001 at 05:48:27PM -0800, Malcolm Fernandes wrote:
> > >> >>
> > >> >>>Hi,
> > >> >>>
> > >> >>>We are using CVS 1.11.1p1 on Solaris.   When we use 'cvs co -D
> > >> date' on
> > >> >>>the Main branch, I noticed that files which were previously 'cvs
> > >> >>>removed' now get checked out in my workspace.     This problem
> > >> does not
> > >> >>>happen on release branches  'cvs co -D date -rREL_X_Y'.
> > >> >>>
> > >> >>>Is this a CVS bug?  Any workarounds?
> > >> >>>
> > >> >>Hi Malcom,
> > >> >>
> > >> >>Not sure I know what behaviour you expect, but as far as I
> > >> >>understand it, when you "cvs remove" a file a new revision is
> > >> >>added to the file with the status "dead".
> > >> >>
> > >> >>If you pull up an older revision of the file, or cause an older
> > >> >>revision to be pulled up because it has a tag or date stamp associated
> > >> >>with it, then the older revision is brought into your working
> > >> directory
> > >> >>because it's status is not "dead".
> > >> >>
> > >> >>I think the basic question is, why do you not want to be able to pull
> > >> >>up an old "snapshot" of the code, as it was at the date/time
> > >> specified,
> > >> >>when you do a "cvs co -D date", including removals and additions?
> > >> >>
> > >> >>What behaviour do you expect?
> > >> >>
> > >> >>HTH,
> > >> >>Rob Helmer
> > >> >>Namodn
> > >> >>
> > >>
> >
> > _______________________________________________
> > Info-cvs mailing list
> > address@hidden
> > http://mail.gnu.org/mailman/listinfo/info-cvs




reply via email to

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