[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Since DST started, cvs update uploads entire sandbox, every time
From: |
Mark D. Baushke |
Subject: |
Re: Since DST started, cvs update uploads entire sandbox, every time |
Date: |
Sun, 16 Mar 2008 12:59:10 -0700 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Arthur Barrett <address@hidden> writes:
> > That said, it is entirely possible that the latest changes in US laws
> > about when the Daylight Savings Time is changed may require that the
> > file be updated.
>
> If that were the case then I would have expected to see more
> discussion about it on the TortoiseCVS, WinCVS and CVSNT newsgroups -
> which I haven't.
This would be true if CVSNT and CVS happened to use exactly the same
code to solve the problem. I honestly do not know if that is true or
not.
> The changes to the DST laws simply altered 'when' the
> change occurs (which changes every year in Australia and many other
> countries so has been tested every year since 2004 outside the US).
I would have thought that CVS was also being tested, but that is by no
means certain as we still receive bug reports from folks running ancient
versions of CVS.
> I really can't see this as being an explanation - unless the CVS 1.11
> changes were never complete - I do suppose most windows users use
> CVSNT.
I was under the impression that the cvs 1.11.19+ and cvs-1.12.11+
releases were fine with regard to the "red file" problem. Of course, I
have no direct experience with it myself. (I stopped using Windows in
2000 and have used various UNIX based operating systems exclusively
since that time, so I am probably not the right person to give
authoritative testimony on what was and was not visible on Windows
systems since that time :-) .)
> If Nelson can test using CVSNT and if the result is that CVSNT doesn't
> have the problem and CVS 1.11 does - then it's a concrete place for
> someone to begin looking ;)
Sure.
> Of course the explanation could be non-DST related. I've seen this
> 'every file stamp wrong' problem when CVS is used with some anti-virus
> software, also if the client and server clocks are sufficiently
> non-synchronised it'll occur too.
Okay. I have never personally seen this problem at all, so I was not
sure what could be driving it given that cvs 1.11.22 did not have any
previously reported problems of this kind.
-- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)
iD8DBQFH3XwOCg7APGsDnFERAvxXAJ0UNHeiohLGDpL4h41nIe+TdEucbwCfWNYN
7czIBx1qum9cvr83VPev2Bg=
=1cTc
-----END PGP SIGNATURE-----