# Proper Publishing of a Repository 4 messages from 2006-03-22 to 2006-03-22. Participants: Jon Loeliger, Timo Hirvonen, Junio C Hamano. Thread: https://gitlist.dev/t/3699 ## Jon Loeliger, 2006-03-22 19:17 Subject: Proper Publishing of a Repository Message-ID: <1143055072.4527.142.camel@cashmere.sps.mot.com> URL: https://gitlist.dev/e/1143055072.4527.142.camel%40cashmere.sps.mot.com ``` 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. Did I miss a step somewhere? Thanks, jdl ``` ## Timo Hirvonen, 2006-03-22 20:16 Subject: Re: Proper Publishing of a Repository Message-ID: <20060322221630.e65baca0.tihirvon@gmail.com> URL: https://gitlist.dev/e/20060322221630.e65baca0.tihirvon%40gmail.com In-Reply-To: <1143055072.4527.142.camel@cashmere.sps.mot.com> ``` On Wed, 22 Mar 2006 13:17:52 -0600 Jon Loeliger 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. -- http://onion.dynserv.net/~timo/ ``` ## Jon Loeliger, 2006-03-22 20:26 Subject: Re: Proper Publishing of a Repository Message-ID: <1143059181.4527.162.camel@cashmere.sps.mot.com> URL: https://gitlist.dev/e/1143059181.4527.162.camel%40cashmere.sps.mot.com In-Reply-To: <20060322221630.e65baca0.tihirvon@gmail.com> ``` On Wed, 2006-03-22 at 14:16, Timo Hirvonen wrote: > On Wed, 22 Mar 2006 13:17:52 -0600 > Jon Loeliger 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 ``` ## Junio C Hamano, 2006-03-22 20:47 Subject: Re: Proper Publishing of a Repository Message-ID: <7v3bha8awl.fsf@assigned-by-dhcp.cox.net> URL: https://gitlist.dev/e/7v3bha8awl.fsf%40assigned-by-dhcp.cox.net In-Reply-To: <1143059181.4527.162.camel@cashmere.sps.mot.com> ``` Jon Loeliger writes: > On Wed, 2006-03-22 at 14:16, Timo Hirvonen wrote: >> Jon Loeliger wrote: >> >> > 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... It really depends on who your audiences are. By packing everything in a single pack, you are optimizing for the initial cloners but punishing incremental updaters. Since your tree is derived from Linus tree, anybody who is interested in your tree is very likely nterested in Linus tree and chances are that she has a recent copy of it locally. In such a case, I would not be surprised if: $ git clone -l -s -n /local-linux-2.6.git/ jdl-linux.git $ cd jdl-linux.git $ git fetch http://jdl.com/jdl-linux.git master:refs/heads/jdl goes a lot faster if you have loose objects around in the repository. ```