Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> writes:
> But the revision.c change might be worth it, if only as a slight band-aid
> for the current issue. It won't fix the original problem, though (because
> that broken repo had a five *year* clock skew, not an hour :)
>
> I'll continue to think about whether I can come up with some sane
> heuristic that allows non-broken cases to not go all the way up to the
> root.
I really wish this was still May 2005. Then I (actually, you)
could just decree:
Sorry guys, but you all need to run convert-objects to
update your repo. What it does is to add a "generation"
header to each and every commit object. Then upgrade
your git to this version, that maintains the
"generation" number, defined as:
(1) parentless commit gets generation #0;
(2) otherwise the generation number of a commit is
max(its parents' generation number)+1.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
