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

Re: Could Git be smarter about object reuse?

From
SSainan <sainan@calamity.inc>
Date
Sep 22, 2025, 22:09 UTC
Message-ID
<ZURUr5sfXi0wsjBeXiwAxyNgalVa2ZveXDgoTcexUNOAgcP_JscHvFFDIss4stpsiB2MzUQ_Z30tFrPSgr8W8V02ecfCj4BFFwQqWwJpba4=@calamity.inc>
In-Reply-To
<20250922200510.GC2205919@coredump.intra.peff.net>
> git repack -adb
Certainly got my fans spinning for a bit. :)
But I can indeed confirm that it does solve the issue at least when amending a commit (will need to do further testing and generally get a feel for it).
However, one issue that I'm immediately noticing is that if I do 'git pull', I get a new pack that is bitmap-less, once again likely exposing me to the same problems.
Repacking before pushing would be okay for me as long as it guarantees a successful push, but it also seems a bit inefficient?
-- Sainan
Previous: Jeff KingNext: Jeff King
Message 5 of 8 in “Could Git be smarter about object reuse?”
  1. SainanSep 22, 2025
  2. Simon RichterSep 22, 2025
  3. SainanSep 22, 2025
  4. Jeff KingSep 22, 2025
  5. SainanSep 22, 2025
  6. Jeff KingSep 23, 2025
  7. SainanOct 3, 2025
  8. SainanOct 3, 2025

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.