{"thread":{"id":"3699","subject":"Proper Publishing of a Repository","startedAt":"2006-03-22T19:17:52Z","lastAt":"2006-03-22T20:47:06Z","messageCount":4,"participants":["Jon Loeliger","Timo Hirvonen","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"17775","messageId":"1143055072.4527.142.camel@cashmere.sps.mot.com","threadId":"3699","inReplyTo":null,"subject":"Proper Publishing of a Repository","fromName":"Jon Loeliger","fromEmail":"jdl@freescale.com","sentAt":"2006-03-22T19:17:52Z","receivedAt":"2006-03-22T19:17:52Z","isPatch":false,"sender":{"key":"jdl@jdl.com","avatar":"https://gravatar.com/avatar/75ce9a10b151acd2c28ec4ab2136dba7b2ff1634530bd04b155981a749d08a64?d=mp&s=160"},"body":"Folks,\n\nSo, I feel like I missed a step in the grand\n\"How To Publish A Repository\" scheme of things.\n\nI made a repo visible over on jdl.com.  No problem.\nBut cloning it took forever.  So I ran \"git-repack\"\non it.  Now cloning only takes hours, not forever.\n\nAll this on the linux kernel over HTTP.\n\nDid I miss a step somewhere?\n\nThanks,\njdl\n"},{"id":"17778","messageId":"20060322221630.e65baca0.tihirvon@gmail.com","threadId":"3699","inReplyTo":"1143055072.4527.142.camel@cashmere.sps.mot.com","subject":"Re: Proper Publishing of a Repository","fromName":"Timo Hirvonen","fromEmail":"tihirvon@gmail.com","sentAt":"2006-03-22T20:16:30Z","receivedAt":"2006-03-22T20:16:30Z","isPatch":false,"sender":{"key":"tihirvon@gmail.com","avatar":null},"body":"On Wed, 22 Mar 2006 13:17:52 -0600\nJon Loeliger <jdl@freescale.com> wrote:\n\n> Folks,\n> \n> So, I feel like I missed a step in the grand\n> \"How To Publish A Repository\" scheme of things.\n> \n> I made a repo visible over on jdl.com.  No problem.\n> But cloning it took forever.  So I ran \"git-repack\"\n> on it.  Now cloning only takes hours, not forever.\n> \n> All this on the linux kernel over HTTP.\n\nUse git:// protocol (git-daemon) if possible.  It is much faster.\n\n-- \nhttp://onion.dynserv.net/~timo/\n"},{"id":"17780","messageId":"1143059181.4527.162.camel@cashmere.sps.mot.com","threadId":"3699","inReplyTo":"20060322221630.e65baca0.tihirvon@gmail.com","subject":"Re: Proper Publishing of a Repository","fromName":"Jon Loeliger","fromEmail":"jdl@freescale.com","sentAt":"2006-03-22T20:26:21Z","receivedAt":"2006-03-22T20:26:21Z","isPatch":false,"sender":{"key":"jdl@jdl.com","avatar":"https://gravatar.com/avatar/75ce9a10b151acd2c28ec4ab2136dba7b2ff1634530bd04b155981a749d08a64?d=mp&s=160"},"body":"On Wed, 2006-03-22 at 14:16, Timo Hirvonen wrote:\n> On Wed, 22 Mar 2006 13:17:52 -0600\n> Jon Loeliger <jdl@freescale.com> wrote:\n> \n> > Folks,\n> > \n> > So, I feel like I missed a step in the grand\n> > \"How To Publish A Repository\" scheme of things.\n> > \n> > I made a repo visible over on jdl.com.  No problem.\n> > But cloning it took forever.  So I ran \"git-repack\"\n> > on it.  Now cloning only takes hours, not forever.\n> > \n> > All this on the linux kernel over HTTP.\n> \n> Use git:// protocol (git-daemon) if possible.  It is much faster.\n\nTrust me, if it were an option, I would.  It isn't.\n\nSo, I think git-prune-packed was the answer here...\njdl\n"},{"id":"17781","messageId":"7v3bha8awl.fsf@assigned-by-dhcp.cox.net","threadId":"3699","inReplyTo":"1143059181.4527.162.camel@cashmere.sps.mot.com","subject":"Re: Proper Publishing of a Repository","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-03-22T20:47:06Z","receivedAt":"2006-03-22T20:47:06Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jon Loeliger <jdl@freescale.com> writes:\n\n> On Wed, 2006-03-22 at 14:16, Timo Hirvonen wrote:\n>> Jon Loeliger <jdl@freescale.com> wrote:\n>>\n>> > All this on the linux kernel over HTTP.\n>> \n>> Use git:// protocol (git-daemon) if possible.  It is much faster.\n>\n> Trust me, if it were an option, I would.  It isn't.\n>\n> So, I think git-prune-packed was the answer here...\n\nIt really depends on who your audiences are.  By packing\neverything in a single pack, you are optimizing for the initial\ncloners but punishing incremental updaters.\n\nSince your tree is derived from Linus tree, anybody who is\ninterested in your tree is very likely nterested in Linus tree\nand chances are that she has a recent copy of it locally.  In\nsuch a case, I would not be surprised if:\n\n\t$ git clone -l -s -n /local-linux-2.6.git/ jdl-linux.git\n        $ cd jdl-linux.git\n        $ git fetch http://jdl.com/jdl-linux.git master:refs/heads/jdl\n\ngoes a lot faster if you have loose objects around in the\nrepository.\n"}]}