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

Re: [RFC] repack vs re-clone

From
Jakub Narebski <jnareb@gmail.com>
Date
Feb 11, 2008, 18:45 UTC
Message-ID
<m3myq7e3ie.fsf@localhost.localdomain>
In-Reply-To
<e5bfff550802100025k616ccff5ib2917d283eeb0ff0@mail.gmail.com>
"Marco Costalba" <mcostalba@gmail.com> writes:
Show 6 quoted lines
> 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.
Repacking without '--force' (for gc) or '--no-reuse-delta' (low level)
would always reuse this tight packing. Only with '--force' you would
waste CPU trying to find better deltaification[*1*].
 
> So it happens to be just faster to re-clone the whole thing by upstream.

So what you are doing is passing the work, unnecessary work I'd say, to some poor server. Not nice.

[*1*] I hope that '--no-reuse-delta' means _try_ to find better delta, but use current one as possible delta, not stupid forget about current deltaification at all...

-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: Nicolas PitreNext: Marco Costalba
Message 3 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.