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

Recommended packing for HTTP repositories

From
Robert Clausecker <fuzxxl@gmail.com>
Date
Feb 13, 2013, 12:38 UTC
Message-ID
<1360759122.6610.15.camel@t520>
Hello!

I provide dumb HTTP access to a git repository on a server where I can't enable the smart HTTP protocol. When the history of the repository grows, should I run git repack to pack all revisions together? Would that cause clients that just want to download a few commit to download the whole pack? What is recommended to do?

Yours, Robert Clausecker
Message 1 of 1 in “Recommended packing for HTTP repositories”
  1. Robert ClauseckerFeb 13, 2013

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.