[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Antwort: Re: Checkout dates

From: <Ralf.Bauer-Malz_at_etas.de>
Date: 2004-03-28 21:21:36 CEST

Greg Hudson <ghudson@MIT.EDU>
03/28/2004 05:36 PM

 
        An: Ralf.Bauer-Malz@etas.de
        Kopie: dev@subversion.tigris.org
        Thema: Re: Checkout dates

On Sun, 2004-03-28 at 10:26, Ralf.Bauer-Malz@etas.de wrote:
> when I do a 'svn co' the creation date of all files of the repository
> are set to the actual date in the working copy. I would have expected
> the original creation date before checkin or at least the checkin date
> of the file.

Why would you have expected that? (Genuine question.)

I expect it as documents should not be changed in any means by a CM
system.

I expected it, too , because other CM software I used before (e.g.
ClearCase) behaved like this.

> This is very annoying, especially if another person checks out my
> repository all of the file dates have gone and set to that new
> checkout date on his/her computer.

Why is this annoying? (Also genuine question.)

Maybe this is just a communicatiuon problem. We used to talk about a
document to change and referred to the file change date. With SVN we must
use version numbers.

For delivered (i.e. exported) documents the file date must be ignored when
diffing later or on another machine.
Our compare tool sets time comparison by default.

The current behavior is motivated by a desire to make "update"
consistent with "checkout". We could set the file dates to the commit
time for a checkout, but "update" would have to use the current time for
changed files, or we would risk causing failures in "make".

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Mar 28 21:22:06 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.