threads / discuss / 18417

git-svn and incorrect working copy file timestamps?

Subject: git-svn and incorrect working copy file timestamps?

## tl;dr

2 messages between Mar 19, 2009 and Mar 19, 2009.

replies: 1people: 1as markdown or json

Derek Mahar· Mar 19, 2009, 19:54 UTC · lore

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· Mar 19, 2009, 21:31 UTC · re: Derek Mahar · lore

Re: git-svn and incorrect working copy file timestamps?

> 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