[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Sun, 4 Nov 2007 12:33:00 -0700
>> Client is 1.11.22. Don't know server version.
> "cvs version" prints out both version numbers.
Thanks. That tells me
Client: Concurrent Versions System (CVS) 1.11.22 (client)
Server: Concurrent Versions System (CVS) 1.11.17 (client/server)
> When did your daylight savings time end? Last Sunday?
No, Just this morning.
> IIRC, CVS determines if a file was changed locally by comparing the
> timestamp with the timestamp in its CVS/Entries files. If your dailight
> savings time ended, the times might be off by one hour, which makes CVS
> believe that everything was changed, and uploading everything to the
> sever in order to let it find out the differences.
I'm pretty sure that there were no time zone offset changes on my system
for at least 6 months until today.
Is that how update normally works? Does it upload the entire contents of
all the files it suspects are changed, and let the server do all the
comparing and diffing (as opposed to let the server download the diffs
between the last-checked-out version and the current repository version
and apply that as a patch locally) ?
Is that behavior configurable? Can I tell it that I do NOT want it to
upload entire source files for updates?
I'm on a asymmetric line where its much faster to pull bits than to push
them (about 15:1), so if I can do updates without uploading, that's preferable.
> If this is the case, the easiest solution for your problem might be to
> just check out a new, fresh sandbox from CVS.
So I tried that, too. Downloaded a fresh sandbox on Friday, then tried to
update it on Saturday. Once again, it uploaded 12.5 Megabytes of sources,
even though there were NO changes to the reprository or to the sandbox
in that interval.
Is this a bug? If so, How should I report it?
Thanks for your help.
Want an e-mail address like mine?
Get a free e-mail account today at www.mail.com!
- (no subject),
Nelson Bolyard <=