Re: CVS file modtime reporting - bug or feature?

Oliver Giesen wrote:
>> Here's the scenario.  Start with a file from CVS that is a 
>> couple years 
>> old, like AUTHORS or COPYING.  The ModTime column properly 
>> reports the 
>> 2004 date.  Now make a trivial change and save it.  The file 
>> timestamp 
>> in the OS is of course updated to the current time, and that gets 
>> reflected in the ModTime column.
>>
>> Finally, select this same file and use the "Update" command 
>> to "get the 
>> clean copy", i.e., revert back to the 2 year old version in CVS.  It 
>> correctly gets the CVS version, but the modtime both in the 
>> filesystem 
>> **and** in CVS/Entries is updated to the time you did the update, not 
>> the original timestamp from CVS!
>>
>> Is this the way it has always worked, or is this a CvsNT bug?  I 
>> certainly wasn't expecting this behavior.
> 
> Yes, that's the way CVS works (not only CVSNT). It only gets the original commit timestamp on initial Checkout, Update will always set it to the time of the last update.
> CVSNT nowadays has a -t option to the Update command (already surfaced in WinCvs on the Update Options tab) which will use the last commit timestamp instead but that requires a CVSNT server as well.

Oliver, thank you for enlightening me.  Sigh, one more thing to add to 
the to-do list for gCvs.  That's really odd, I wonder why CVS elected to 
  do it that way.  It has the real timestamp, obviously, since it got it 
on initial checkout.

-- 
Guy Rouillier


 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/cvsgui-dev/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/