Re: [BUG] "git describe --match" performance

From: Taylor Blau <me@ttaylorr.com>
Date: Oct 31, 2024, 19:00 UTC
Message-ID: <ZyPTxgSFiQpZG8qe@nand.local>
In-Reply-To: <20241031114731.GA608553@coredump.intra.peff.net>

On Thu, Oct 31, 2024 at 07:47:31AM -0400, Jeff King wrote:

> I think we'll build the commit graph file by default these days when you
> run "git gc". But we don't build it immediately after cloning. Perhaps
> we should change that.

I think that would be a reasonable thing to do. We already have fetch.writeCommitGraph and gc.writeCommitGraph, so it seems like a natural extension to add clone.writeCommitGraph.

I don't have a strong feeling about what the default should be, although I err on the side of "true". Most repositories cloned will be small enough that writing a commit-graph upon clone shouldn't take too long. So the savings it will provide will be well worth the marginal increase in perceived clone time.

Thanks, Taylor