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

Re: Repacking a repository uses up all available disk space

From
Nasser Grainawi <nasser@codeaurora.org>
Date
Jun 13, 2016, 01:43 UTC
Message-ID
<C04883EB-2170-47C3-94E7-AE13516FD0C0@codeaurora.org>
In-Reply-To
<20160612221309.GC5428@sigill.intra.peff.net>
On Jun 12, 2016, at 4:13 PM, Jeff King <peff@peff.net> wrote:
Show 10 quoted lines
> 
>    At GitHub we actually have a patch to `repack` that keeps all
>    objects, reachable or not, in the pack, and use it for all of our
>    automated maintenance. Since we don't drop objects at all, we can't
>    ever have such a race. Aside from some pathological cases, it wastes
>    much less space than you'd expect. We turn the flag off for special
>    cases (e.g., somebody has rewound history and wants to expunge a
>    sensitive object).
> 
>    I'm happy to share the "keep everything" patch if you're interested.
We have the same kind of patch actually (for the same reason), but back on the shell implementation of repack. It'd be great if you could share your modern version.
Nasser
-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, 
a Linux Foundation Collaborative Project
Previous: Jeff KingNext: Jeff King
Message 7 of 11 in “Repacking a repository uses up all available disk space”
  1. Konstantin RyabitsevJun 12, 2016
  2. Jeff KingJun 12, 2016
  3. Konstantin RyabitsevJun 12, 2016
  4. Jeff KingJun 12, 2016
  5. Duy NguyenJun 13, 2016
  6. Jeff KingJun 13, 2016
  7. Nasser GrainawiJun 13, 2016
  8. 0/3 repack --keep-unreachableJeff King, Jun 13, 2016
  9. 1/3 repack: document --unpack-unreachable optionJeff King, Jun 13, 2016
  10. 2/3 repack: add --keep-unreachable optionJeff King, Jun 13, 2016
  11. 3/3 repack: extend --keep-unreachable to loose objectsJeff King, Jun 13, 2016

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.