{"thread":{"id":"18417","subject":"git-svn and incorrect working copy file timestamps?","startedAt":"2009-03-19T19:54:12Z","lastAt":"2009-03-19T21:31:43Z","messageCount":2,"participants":["Derek Mahar"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"108572","messageId":"1237492452300-2505059.post@n2.nabble.com","threadId":"18417","inReplyTo":null,"subject":"git-svn and incorrect working copy file timestamps?","fromName":"Derek Mahar","fromEmail":"derek.mahar@gmail.com","sentAt":"2009-03-19T19:54:12Z","receivedAt":"2009-03-19T19:54:12Z","isPatch":false,"sender":{"key":"derek.mahar@gmail.com","avatar":"https://gravatar.com/avatar/a9d015b9d56f78bf39d358cf85fd39e04bbbe2c9b936165b453a4ba82c5e85b2?d=mp&s=160"},"body":"\nShould \"git svn\" not preserve the file timestamps of the original commit tree\nin the working copy?  Using Git 1.6.2.1, built from source, I find that \"git\nsvn clone\" sets the file timestamps in the working copy to the current date. \nI expected the timestamps to match those of the tree as it was originally\ncommitted.  I get this result using both Cygwin and Crunchbang Linux 8.10.02\n(an Ubuntu derivative).\n\nDerek\n-- \nView this message in context: http://n2.nabble.com/git-svn-and-incorrect-working-copy-file-timestamps--tp2505059p2505059.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"108587","messageId":"5f4b18bf0903191431t20313bb4u14a717fecc27f18@mail.gmail.com","threadId":"18417","inReplyTo":"1237492452300-2505059.post@n2.nabble.com","subject":"Re: git-svn and incorrect working copy file timestamps?","fromName":"Derek Mahar","fromEmail":"derek.mahar@gmail.com","sentAt":"2009-03-19T21:31:43Z","receivedAt":"2009-03-19T21:31:43Z","isPatch":false,"sender":{"key":"derek.mahar@gmail.com","avatar":"https://gravatar.com/avatar/a9d015b9d56f78bf39d358cf85fd39e04bbbe2c9b936165b453a4ba82c5e85b2?d=mp&s=160"},"body":"> Should \"git svn\" not preserve the file timestamps of the original commit tree\n> in the working copy?\n\nI learned from http://marc.info/?l=git&m=122783905206964&w=2 that all\nGit commands do not preserve file timestamps because Git, by design,\ndoes not record timestamps in the tree objects.  So, in order to see\nthe last time a particular file changed, you must examine the commit\nlog.  I guess I'll just have to get used to ignoring the working copy\nfile timestamps.\n\nDerek\n"}]}