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

[Gregory L Priem]

On Tue, 26 Sep 2000 14:16:14 -0700, Donald Sharp wrote:

>Why don't you just fix vss2rcs.js to check the date returned by vss
>and if it's greater than what could even remotely be possible change
>it to a sane value?  Seems like a lot of work to hack cvs when you
>should just hack the input script...

I probably should have mentioned that that was what i originally
tried, but it got more complicated, since this is not just restricted
to the year being goofy. [the 2020 stuff is not really difficult to
take care of, as most of them were 'really' 1998. There are also some
dates of 2000 (probably doing y2k testing and forgetting to turn the
date back), which are not as easy to identify as being 'bad']

The complication can perhaps been seen in a multiple developer
environment with the developers in multiple time zones, since VSS does
not have any time-normalizing or control. 

Here is one sequence which is in our vss:

1. Developer A checks in source, 5pm his time, and then leaves for
home. 
2. Developer B [in time zone 1 hour behind developer A] finds bug in
source, fixes it and checks it in, 4:30pm his time. 

catching and trying to fix all of them up would be a nightmare. much
quicker, but less desirable, would be to use the current date/time
when checking in the files, but then the full span of time would be
lost in the conversion [oh - i fixed that bug while you were on
sabbatical last year]

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. 

i figured, since rcs appears to be gpl, that source _should_ have been
available at some point and someone might have it. 



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