From: Jon Smirl Date: Sat, 09 Sep 2006 22:54:34 GMT Subject: Re: Change set based shallow clone Message-ID: <9e4733910609091554m2a8a001axd575defff9a0e7a9@mail.gmail.com> In-Reply-To: On 9/9/06, Linus Torvalds 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