[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Incorrect 'Entries' timestamp?
From: |
Duncan Sommerville |
Subject: |
Re: Incorrect 'Entries' timestamp? |
Date: |
Fri, 21 Dec 2001 16:14:25 +0000 |
At 09:42 21/12/01 -0500, you wrote:
>Incorrect 'Entries' timestamp?
>
>I searched the internet and newsgroups, but I can't find any detailed
>information on 'Entries' files and timestamps.
http://www.cvshome.org/docs/manual/cvs_2.html#IDX38
>When I checkout a module, the file list in the 'Entries' file has timestamp
>set to current time for all files . When I run 'cvs status', the timestamps
>are changed to the commit time of each file.
>Is this the way it's supposed to work?
I'm no expert, but I don't think so...
>WinCVS shows the file as red (modified) after checkout (i.e. I guess this
>means WinCVS considers a file modified if modification date differs from
>the date in the 'Entries' file) .
>If I perform 'cvs status' from cmd, or performs an update from WinCVS, the
>'Entries' file is updated with modification date of CVS file (,v).
Strangely enough I've been looking at a similar problem with a bespoke CVS
client I've written - in particular getting it to work with WinCVS.
One of the things I noticed is that the command-line cvs client (on UNIX
anyway) stores the timestamp in Entries in the following format:
Mon Jan 1 2001 12:00:00
...whereas WinCVS stores/expects the timestamp to be in the following format:
Mon Jan 01 2001 12:00:00
WinCVS doesn't appear to recognise the first date-format, so marks the file as
modified...
Kind regards,
Duncan.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com