Re: [External] Re: git-blame extremely slow in partial clones due to serial object fetching

From: Shubham Kanodia <shubham.kanodia10@gmail.com>
Date: Nov 22, 2024, 08:51 UTC
Message-ID: <dd8b5cdb-2ce8-4ad6-ae96-197fa898b206@gmail.com>
In-Reply-To: <xmqqv7wf8ydw.fsf@gitster.g>

On 22/11/24 1:59 pm, Junio C Hamano wrote:

Show 11 quoted lines

> Shubham Kanodia <shubham.kanodia10@gmail.com> writes:
> 
>> Junio — would it make sense to add an option (and config) for `git
>> blame` that limits how far back it looks for fetching blobs?
> 
> No, I do not think it would.
> 
> What would our workaround for the next one when people say "oh, 'git
> log -p' fetches blobs on demand and latency kills me"?  Yet another
> such an option only for 'git log'?
>

I'm guessing `git log` already provides options to limit history using `-n` or `--since` so ideally its not unbounded if you use those, unlike with `git blame`?

I understand our concerns regarding adding new config options though. Between the solutions discussed in this thread — batching, adding server side support, (or another) — what do you think could be a good track to pursue here because this makes using `git blame` on larger partially cloned repos a possible footgun.