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

Could Git be smarter about object reuse?

From
SSainan <sainan@calamity.inc>
Date
Sep 22, 2025, 10:06 UTC
Message-ID
<pmKix6R7b3WVLrcK6ig1Lh7RhrB5G4Hm5yam_fEoC839aatB-OjJEmSJJ-weErGEnt4Mvgf5slxgu6Pm1xlGZ4mr_i4MIAAEMYy8DjJnWgk=@calamity.inc>
Hello, I'm not entirely sure about the details of pushing, but I've noticed that basically it just uploads every object the server might need in relationship to that commit which can be a huge amount of data and sometimes even exceed the server-defined request timeout, causing the push to fail.
It's especially annoying because I know the server already has basically all the blobs needed and hence would only need to receive the commit and tree objects.
Are there any hidden flags or future cosiderations that could be made to reduce the bandwidth needed for such pushes?
-- Sainan
Next: Simon Richter
Message 1 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.