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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Sun Sep 10 08:55:58 2006
This archive was generated by hypermail 2.1.8 : 2006-09-10 08:56:39 EST