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

Re: [PATCH] [RFC] Generational repacking

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Jun 7, 2007, 22:51 UTC
Message-ID
<46a038f90706071551w45592471g59a35abb871749bd@mail.gmail.com>
In-Reply-To
<46687A73.6080100@vilain.net>
On 6/8/07, Sam Vilain <sam@vilain.net> wrote:
> Ok.  But if repack is generational you probably don't mind waiting for
> it on commit so don't need to background it.

Agreed. The patch I posted back then was on fetch as a signle fetch is more likely to bring a lot of new objects in. (Moreso than a commit)

Repack-on-commit if there's more than 1k unpacked objects makes sense. Are fetches nowaways always using the "keep pack" and "fatten thin pack" semantics? If yes, then

cheers,
martin
Previous: Sam VilainNext: Nicolas Pitre
Message 12 of 13 in “[RFC] Generational repacking”
  1. [RFC] Generational repackingSam Vilain, Jun 6, 2007
  2. Junio C HamanoJun 6, 2007
  3. Sam VilainJun 6, 2007
  4. Dana HowJun 7, 2007
  5. Sam VilainJun 7, 2007
  6. Nicolas PitreJun 7, 2007
  7. Sam VilainJun 7, 2007
  8. Nicolas PitreJun 7, 2007
  9. Sam VilainJun 7, 2007
  10. Martin LanghoffJun 7, 2007
  11. Sam VilainJun 7, 2007
  12. Martin LanghoffJun 7, 2007
  13. Nicolas PitreJun 7, 2007

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.