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

Compressing packed-refs

From
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Date
Jul 16, 2020, 22:10 UTC
Message-ID
<20200716221026.dgduvxful32gkhwy@chatter.i7.local>
Hi, all:

I know repos with too many refs is a corner-case for most people, but it's looming large in my world, so I'm wondering if it makes sense to compress the packed-refs file when "git pack-refs" is performed?

What would the implications be, other than minor performance degradation when reading it?

-K
Next: Junio C Hamano
Message 1 of 6 in “Compressing packed-refs”
  1. Konstantin RyabitsevJul 16, 2020
  2. Junio C HamanoJul 16, 2020
  3. Konstantin RyabitsevJul 16, 2020
  4. Jeff KingJul 17, 2020
  5. Konstantin RyabitsevJul 18, 2020
  6. Jeff KingJul 20, 2020

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.