Re: [PATCH 1/1] fetch: add fetch.writeCommitGraph config setting
- From
Jeff King <peff@peff.net>
- Date
- Sep 6, 2019, 19:16 UTC
- Message-ID
- <20190906191622.GA7096@sigill.intra.peff.net>
- In-Reply-To
- <xmqq1rwtnv03.fsf@gitster-ct.c.googlers.com>
On Fri, Sep 06, 2019 at 11:24:12AM -0700, Junio C Hamano wrote:
Show 11 quoted lines
> Jeff King <peff@peff.net> writes: > > > Sure, but wouldn't that similarly apply to fetching? What is it that > > makes bursts of pushes more likely than bursts of fetches? > > Because people tend to use a repository as a gathering point? You > may periodically fetch from and push to a repository, and you may > even do so at the same interval, but simply because there are more > "other" people than you alone as a single developer in the project, > your fetch tends to grab work from more people than yoru push that > publish your work alone?
I suppose so. But I think the "stock git without any other job infrastructure" case would still benefit. How do we know when the burst is done? We'd effectively be relying on auto-gc to do that, but "enough packs to merit gc" and "burst is done, now is a good time to update the commit graph" are two different metrics.
-Peff