On Wed, 2006-07-12 at 02:51 +0100, Bruce Stephens wrote: > "Zack Weinberg" <[EMAIL PROTECTED]> writes: > > > I was thinking about using commit date as a further heuristic, i.e. > > when we have two LCAs neither of which is an ancestor of the other, > > merge the newest one first; furthermore, when we have three or more > > heads with the same LCA, merge the newest two first. However, it > > seems like a huge pain to get from a revision_id to its commit date, > > and in fact I'm not sure the date cert is guaranteed to exist. > > I think mtn always creates a date cert. There may be more than one, > of course (with different values), so there's a certain amount of > flexibility in how you might determine the "newest two".
It will always generate one, yes. But it's perfectly valid for there not to be one (probably can only happen with 'db execute'), or as Bruce said for there to be more than one. So don't rely on there being a unique date cert, or even there being a date cert at all. Tim _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
