git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Derek Mahar <derek.mahar@gmail.com>
Date
Mar 19, 2009, 21:31 UTC
Message-ID
<5f4b18bf0903191431t20313bb4u14a717fecc27f18@mail.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
Previous: Derek Mahar
Message 2 of 2 in “git-svn and incorrect working copy file timestamps?”
  1. Derek MaharMar 19, 2009
  2. Derek MaharMar 19, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.