git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Shubham Kanodia <shubham.kanodia10@gmail.com>
Cc: Han Young <hanyang.tony@bytedance.com>,
	 Jonathan Tan <jonathantanmy@google.com>,
	 Burke Libbey <burke.libbey@shopify.com>,
	git@vger.kernel.org
Subject: Re: [External] Re: git-blame extremely slow in partial clones due to serial object fetching
Date: Fri, 22 Nov 2024 17:29:31 +0900	[thread overview]
Message-ID: <xmqqv7wf8ydw.fsf@gitster.g> (raw)
In-Reply-To: <972d0904-650b-4161-a13c-e3081d55a212@gmail.com> (Shubham Kanodia's message of "Fri, 22 Nov 2024 09:02:08 +0530")

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'?


  reply	other threads:[~2024-11-22  8:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19 20:16 git-blame extremely slow in partial clones due to serial object fetching Burke Libbey
2024-11-20 11:59 ` Manoraj K
2024-11-20 18:52 ` Jonathan Tan
2024-11-20 22:55   ` Junio C Hamano
2024-11-21  3:12     ` [External] " Han Young
2024-11-22  3:32       ` Shubham Kanodia
2024-11-22  8:29         ` Junio C Hamano [this message]
2024-11-22  8:51           ` Shubham Kanodia
2024-11-22 17:55             ` Jonathan Tan
2024-11-25  0:22               ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqv7wf8ydw.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=burke.libbey@shopify.com \
    --cc=git@vger.kernel.org \
    --cc=hanyang.tony@bytedance.com \
    --cc=jonathantanmy@google.com \
    --cc=shubham.kanodia10@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).