On 2008-02-05 21:30:38 -0800, Junio C Hamano wrote:
> 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.
Would it be possible to start adding a generation header to new
commits, so that this problem (and others -- I recall hearing this
same wish a year or two ago regarding some gitk toposorting issue)
will eventually fade away?
For old commits without an embedded generation number, git could
conceivably compute their generation number once and store them in a
(local) file somewhere.
I expect that this has been considered already, and I'd be interested
in hearing why it doesn't work, if you (or someone else) have some
time to waste. :-)
--
Karl Hasselström, kha@xxxxxxxxxxx
www.treskal.com/kalle
-
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
