Re: topological index field for commit objects
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Jul 5, 2016, 11:43 UTC
- Message-ID
- <alpine.DEB.2.20.1607051339040.8378@virtualbox>
- In-Reply-To
- <20160629223007.GA4726@sigill.intra.peff.net>
Hi Peff,
On Wed, 29 Jun 2016, Jeff King wrote:
> I haven't thought hard specifically about merge bases computation, so > perhaps that is a case that isn't helped at all.
I guess it is not helped by generation numbers.
But then, we often ask: "is commit A an ancestor of commit B" e.g. to check whether we can fast-forward. The way we do it now is to compute the merge base (singular: if there are more than one, we stop at the first one we found) and then look whether commit A is identical to the merge base.
If we had generation numbers available, then we would have to change those computations in order to benefit from them when determining ancestry.
But then, reachability would accelerate that even more than generation numbers.
Ciao, Dscho