git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 22, 2024, 08:29 UTC
Message-ID
<xmqqv7wf8ydw.fsf@gitster.g>
In-Reply-To
<972d0904-650b-4161-a13c-e3081d55a212@gmail.com>
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'?

Previous: Shubham KanodiaNext: Shubham Kanodia
Message 7 of 10 in “git-blame extremely slow in partial clones due to serial object fetching”
  1. Burke LibbeyNov 19, 2024
  2. Manoraj KNov 20, 2024
  3. Jonathan TanNov 20, 2024
  4. Junio C HamanoNov 20, 2024
  5. Han YoungNov 21, 2024
  6. Shubham KanodiaNov 22, 2024
  7. Junio C HamanoNov 22, 2024
  8. Shubham KanodiaNov 22, 2024
  9. Jonathan TanNov 22, 2024
  10. Junio C HamanoNov 25, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.