# git-svn and incorrect working copy file timestamps?

2 messages from 2009-03-19 to 2009-03-19. Participants: Derek Mahar.
Thread: https://gitlist.dev/t/18417

## Derek Mahar, 2009-03-19 19:54

Subject: git-svn and incorrect working copy file timestamps?
Message-ID: <1237492452300-2505059.post@n2.nabble.com>
URL: https://gitlist.dev/e/1237492452300-2505059.post%40n2.nabble.com

```

Should "git svn" not preserve the file timestamps of the original commit tree
in the working copy?  Using Git 1.6.2.1, built from source, I find that "git
svn clone" sets the file timestamps in the working copy to the current date. 
I expected the timestamps to match those of the tree as it was originally
committed.  I get this result using both Cygwin and Crunchbang Linux 8.10.02
(an Ubuntu derivative).

Derek
-- 
View this message in context: http://n2.nabble.com/git-svn-and-incorrect-working-copy-file-timestamps--tp2505059p2505059.html
Sent from the git mailing list archive at Nabble.com.

```

## Derek Mahar, 2009-03-19 21:31

Subject: Re: git-svn and incorrect working copy file timestamps?
Message-ID: <5f4b18bf0903191431t20313bb4u14a717fecc27f18@mail.gmail.com>
URL: https://gitlist.dev/e/5f4b18bf0903191431t20313bb4u14a717fecc27f18%40mail.gmail.com
In-Reply-To: <1237492452300-2505059.post@n2.nabble.com>

```
> Should "git svn" not preserve the file timestamps of the original commit tree
> in the working copy?

I learned from http://marc.info/?l=git&m=122783905206964&w=2 that all
Git commands do not preserve file timestamps because Git, by design,
does not record timestamps in the tree objects.  So, in order to see
the last time a particular file changed, you must examine the commit
log.  I guess I'll just have to get used to ignoring the working copy
file timestamps.

Derek

```