info-cvs
[Top][All Lists]
Advanced

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

Re: source code for rcs57nt / cvs-1.9-win?


From: Gregory L Priem
Subject: Re: source code for rcs57nt / cvs-1.9-win?
Date: Tue, 26 Sep 2000 15:41:23 -0700

On Tue, 26 Sep 2000 15:00:41 -0700, Donald Sharp wrote:
>On Tue, Sep 26, 2000 at 02:50:24PM -0700, Gregory L Priem wrote:
>> with the rcs 5.7 ci.c source, it seems like it does a simple check for
>> date, sends a message, and does a 'continue'. a simple commenting out
>> of the continue may be a usable kludge. 
>
>This will break other cvs commands.  Lots of cvs commands depend on the
>date
>time stamp increasing from oldest->newest.  With this kludge you'll
>be able to get the information in.  But you will not be
>able to get the information out in a meaningfull manner.  Suppose
>
>I have a file with these version- timestamps:
>
>1.1 - 09-01-2000
>1.2 - 08-01-2000
>1.3 - 09-03-2000
>1.4 - 09-04-2000
>
>Now suppose I do a diff of this file versus the contents of the file
>on 09-01-2000.  CVS now would only diff versus the 1.2 version of the
>file versus the correct version that would be 1.1.  This is just one
>example of where cvs would fail.
>
>It's better to not be able to ask these questions instead of asking
>these questions and just getting *wrong* information.  The more I think
>about it.  If you can't guarantee the correct time as you import than 
>you shouldn't import the time stamps( just say it's lost ).

You're right, of course. I am so used to the 'vss way' that I have
never considered cvs's ability of doing things by date; with vss i
just did things by label [grabbing a snapshot] and by specific
revision [when looking through changes].

i'd _still_ like to find the source code, though ;) 


greg priem                         kb0erz
address@hidden
bark, fido, bark [neither of us speak for my employer]



reply via email to

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