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

Re: Proper Publishing of a Repository

From
Jon Loeliger <jdl@freescale.com>
Date
Mar 22, 2006, 20:26 UTC
Message-ID
<1143059181.4527.162.camel@cashmere.sps.mot.com>
In-Reply-To
<20060322221630.e65baca0.tihirvon@gmail.com>
On Wed, 2006-03-22 at 14:16, Timo Hirvonen wrote:
Show 15 quoted lines
> On Wed, 22 Mar 2006 13:17:52 -0600
> Jon Loeliger <jdl@freescale.com> wrote:
> 
> > Folks,
> > 
> > So, I feel like I missed a step in the grand
> > "How To Publish A Repository" scheme of things.
> > 
> > I made a repo visible over on jdl.com.  No problem.
> > But cloning it took forever.  So I ran "git-repack"
> > on it.  Now cloning only takes hours, not forever.
> > 
> > All this on the linux kernel over HTTP.
> 
> Use git:// protocol (git-daemon) if possible.  It is much faster.
Trust me, if it were an option, I would.  It isn't.

So, I think git-prune-packed was the answer here... jdl

Previous: Timo HirvonenNext: Junio C Hamano
Message 3 of 4 in “Proper Publishing of a Repository”
  1. Jon LoeligerMar 22, 2006
  2. Timo HirvonenMar 22, 2006
  3. Jon LoeligerMar 22, 2006
  4. Junio C HamanoMar 22, 2006

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.