Re: Change set based shallow clone

From: Jon Smirl <jonsmirl@gmail.com>
Date: Sep 9, 2006, 22:54 UTC
Message-ID: <9e4733910609091554m2a8a001axd575defff9a0e7a9@mail.gmail.com>
In-Reply-To: <Pine.LNX.4.64.0609091433460.27779@g5.osdl.org>

On 9/9/06, Linus Torvalds <torvalds@osdl.org> wrote:

> However, it's just a heuristic. "Most recent date" is not well-defined in
> a distributed environment that doesn't have a global clock. If somebody
> does commits on a machine that has the clock just set wrong, "most recent"
> may well not be _really_ recent.

When a merge happens could git fix things up in the database by adding a corrected, hidden time stamp that would keep things from having an out of order time sequence? That way you wouldn't need to rediscover the out of order commit each time the tree is generated.

-- 
Jon Smirl
jonsmirl@gmail.com

$ 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.