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

Re: mod-times (was: keyword expansion)

From
Linus Torvalds <torvalds@osdl.org>
Date
Apr 26, 2005, 00:34 UTC
Message-ID
<Pine.LNX.4.58.0504251732410.18901@ppc970.osdl.org>
In-Reply-To
<200504251756.j3PHuSh01362@unix-os.sc.intel.com>
On Mon, 25 Apr 2005 tony.luck@intel.com wrote:
Show 5 quoted lines
> 
> One way to do this would be to rip on some of the core fundamentals of GIT
> and store the time that an object was created inside the object. E.g.
> 
>    blob size secs-since-1970 ...
You really don't want that.

The thing is, somebody doing a "touch" on a file should _not_ cause that tree to be committed as a new tree.

Trying to save mtime in a git archive is about a million times worse than saving the whole "mode" information, and there we already ended up cutting it down to just one bit, exactly because it was horrible not to.

So this is not about git formats, this is about it just not being practical to do. Git simply isn't a good thing to store mtime in.

			Linus
Previous: Geert Bosch
Message 5 of 5 in “keyword expansion”
  1. Thomas GlanzmannApr 25, 2005
  2. mod-times (was: keyword expansion)tony.luck@intel.com, Apr 25, 2005
  3. Thomas GlanzmannApr 25, 2005
  4. Geert BoschApr 25, 2005
  5. Linus TorvaldsApr 26, 2005

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.