[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Incorrect 'Entries' timestamp?
From: |
Thomas Eliasson |
Subject: |
Incorrect 'Entries' timestamp? |
Date: |
Fri, 21 Dec 2001 15:07:04 +0100 |
Hi!
I searched the internet and newsgroups, but I can't find any detailed
information on 'Entries' files and timestamps.
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?
When is a file modified?
- if working copy's date is later than the date in the 'Entries' file
- or is the criteria simply that times should differ?
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).
According to 'Cederqvist':
timestamp is the timestamp of the file at the time that cvs created it; if
the timestamp differs with the actual modification time of the file it
means the file has been modified.
I assume that 'the time that cvs created it' means the time for last commit.
If I understand this correct, checkout writes wrong timestamp into the
'Entries' file.
I'm using WinCVS 1.2 and it's cvs.exe
cvs -version reports:
Concurrent Versions System (CVS) 1.11 (client)
Copyright (c) 1989-2000 Brian Berliner, david d `zoo' zuhn,
Jeff Polk, and other authors
OS is Windows 2000 Professional (Swedish).
Can anyone shed some light on this?
Thanks!
/Thomas Eliasson
- Incorrect 'Entries' timestamp?,
Thomas Eliasson <=