Re: Performance issue: initial git clone causes massive repack

From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Apr 7, 2009, 10:11 UTC
Message-ID: <46a038f90904070311n6606e678y43f716cbc05a397f@mail.gmail.com>
In-Reply-To: <20090405225954.GA18730@vidovic>

On Mon, Apr 6, 2009 at 12:59 AM, Nicolas Sebrecht <nicolas.s-dev@laposte.net> wrote:

> What about the rsync solution given in this thread?

Also, HTTP is excellent for initial clones, possibly better than rsync in some cases.

The Gentoo team has good reasons to do things their way, and it's IMHO a wart in git that initial clones of large repos. But we do have valid workarounds (as above) so they can use them .

cheers,

martin

-- 
 martin.langhoff@gmail.com
 martin@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff

$ 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.