Donald Sharp <[EMAIL PROTECTED]> writes:
> If you can't guarantee the correct time as you import than
> you shouldn't import the time stamps( just say it's lost ).
Or, modify the script to first get the dates for every revision of a
file, then "normalize" all those dates, store them in an array, and
use those dates during the conversion. You could do something like:
* start at the final revision - if its date is > current,
set it to the current date
* For each previous version, make sure its date is at most one
second prior to the next higher revision's date.
As long as your only date problem is with dates set too far into the
future, this should give you something reasonably workable.
BTW, does this vss2rcs.js script handle updating already existing RCS
files with new revisions from VSS, or do you start over from scratch
every day?
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
