On Wed, Jul 02, 2003 at 03:23:59PM -0500, Arachtingi, Mike wrote: > I'm confused about the date that W2K shows for a file in my sandbox, > after I commit it. I understand that CVS keeps track by UTC, but why > doesn't my OS show the current time, local, that the file was last > changed? - BTW, this doesn't happen if the file does not have any > keywords.
Right. To do the keyword substitution, CVS has to rewrite the file in your sandbox; hence, the written-to date changes accordingly. If there are no keywords in the file (or if keyword substitution is disabled), CVS doesn't bother rewriting the file, so the date doesn't change. So that part of what you're seeing makes perfect sense. > For example, I edited and committed a file named LH.java, containing the > keyword $Name:$. Note that before the commit, the local timestamp of > the file was today, 1:42 PM Central US. After, the OS reports that the > time is 12:05 AM tomorrow. Does this seem wrong? I don't know. I just tested it on Linux, and CVS (1.11.2.1, in case it matters) explicitly (using utime()) set the sandbox file's timestamp to the current *local* time of the commit operation. (The new revision in the repo is dated in UTC of course.) I'd naively expect the same under Windows, but I'm not familiar enough with that situation to know what else might be going on. What time was it when you did the commit? What time did your W2K client think it was? What time did the server think it was? -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont. [EMAIL PROTECTED] | | / When I came back around from the dark side, there in front of me would be the landing area where the crew was, and the Earth, all in the view of my window. I couldn't help but think that there in front of me was all of humanity, except me. - Michael Collins, Apollo 11 Command Module Pilot _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs