Re: My first stumper ...

[Larry Jones]

Laine Stump writes:
> 
> And *that* causes a problem of its own in another circumstance. While
> playing with vss2cvs, I found that (on WinNT) if you do a commit,
> modify a file, then do another commit within 1 second, the commit will
> do nothing since CVS believes that the file is unmodified.

CVS tries to avoid this problem by sleeping until the time is later than
the timestamp of the most recent file before it exits.  This works
perfectly on Unix-like systems where file timestamps have the same
granularity as time() does.  Unfortunately, the FAT filesystem (and
presumably NTFS as well) has a timestamp granularity of two seconds
whereas time()'s granularity is only one second, so there's a one second
window for error.  I've thought about changing it to sleep until at
least two seconds have elapsed, but I'm not sure that's such a good idea
-- it's not necessary on Unix and it may not be sufficient for some
other obscure system.

> I don't know if there's any practical way to get around this, other
> than forcing the commit with -f (that's what I did).

You can always touch the file and do a normal commit.

-Larry Jones

Hello, I'm wondering if you sell kegs of dynamite. -- Calvin