Hi All,
I've found a one issue related to CVS update high traffic if local files stored
on FAT volumes.
Let's take a simple example:
Mozilla.org have an CVS server to allow everybody obtain sources of new
generation of browser. I good programmer from Ukraine (like me ;o) have a
W'95(W'98,NT,W2K - does't care) mashine @home and wanna join activity for open
source.
That he will do. First of all he will download current version of CVS files to
his __FAT__ volume via some CVS nigtly shapshot. After it he will try make cvs
update and will be wondering why it take so long time to update 12 hours
changes ????
Here is an answer : FAT does't allow wrote notodd number of seconds in
modification time (for example you will never be able set 17 Feb 2000 8:00:31
as modification time to any file on FAT volume). It's a very old story why MS
used 32bit timestamp but we need to change something in CVS to prevent sending
half of files again to CVS server during update.
I'm not so familar with C so i can't send a patch.
I only propose - change a Classify_File in classify.c (or No_Difference in
no_diff.c) to don't send a file to server if only 1 sec diff in modification
time. I think we can add this to Win32 client version of cvs and leave *nix
versions alone.
How about it ?? Is it fixed or already reported ??
Andrew G. Tereschenko
Odessa, Ukraine
__________________________________________________
Do You Yahoo!?
Send online invitations with Yahoo! Invites.
http://invites.yahoo.com
