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

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

From
GOGuido Ostkamp <git@ostkamp.fastmail.fm>
Date
Mar 19, 2009, 23:02 UTC
Message-ID
<alpine.LSU.2.01.0903192355590.29898@bianca.dialin.t-online.de>
Show 6 quoted lines
> 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.

As far as I know setting the current time is required when switching between different named branches in the same repository.

It can happen that a branch switch ('checkout' in Git's terminology) retrieves an older version of a source file, and then the Makefile would not detect that an object file (a result from earlier compilation that is of course not stored in the repo itself) has to be rebuild because this is based on time checks only. In order to avoid this, the source file (even if older) gets the current date, so it is in any case newer than the object file and causes an automatic rebuild.

Regards
Guido
Message 1 of 1 in “Re: git-svn and incorrect working copy file timestamps?”
  1. Guido OstkampMar 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.