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

[RFC] repack vs re-clone

From
MCMarco Costalba <mcostalba@gmail.com>
Date
Feb 10, 2008, 08:25 UTC
Message-ID
<e5bfff550802100025k616ccff5ib2917d283eeb0ff0@mail.gmail.com>

Sometime I found myself re-cloning entirely a repository, as example the Linux tree, instead of repackaging my local copy.

The reason is that the published Linux repository is super compressed and to reach the same level of compression on my local copy I would need to give my laptop a long night running.

So it happens to be just faster to re-clone the whole thing by upstream.

Also repackaging a big repo in the optimal way is not so trivial, you need to understand quite advanced stuff like window depth and so on and probably the pack parameters used upstream are easily better then what you could 'guess' trying yourself. Or simply you don't have enough RAM as would be needed.

On the other end it would be interesting to know, before to start the new clone, what is the real advantage of this, i.e. what is the repository size upstream.

So I would like to ask if anyone would consider useful:
- A command like 'git info' or something like that that prints size of
local and upstream repository (among possibly other things)
- An option like 'git repack --clone' to instruct git to download and
use current upstream packs instead of trying to recreate new ones.
Marco
Next: Nicolas Pitre
Message 1 of 9 in “[RFC] repack vs re-clone”
  1. Marco CostalbaFeb 10, 2008
  2. Nicolas PitreFeb 10, 2008
  3. Jakub NarebskiFeb 11, 2008
  4. Marco CostalbaFeb 11, 2008
  5. Johannes SchindelinFeb 11, 2008
  6. Jakub NarebskiFeb 11, 2008
  7. Nicolas PitreFeb 11, 2008
  8. Nicolas PitreFeb 11, 2008
  9. Jakub NarebskiFeb 11, 2008

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.