{"thread":{"id":"1988","subject":"time to update with new packs","startedAt":"2005-10-01T04:40:23Z","lastAt":"2005-10-01T07:18:59Z","messageCount":2,"participants":["Tony Luck","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"9577","messageId":"12c511ca0509302140o4263020bsc337594609175173@mail.gmail.com","threadId":"1988","inReplyTo":null,"subject":"time to update with new packs","fromName":"Tony Luck","fromEmail":"tony.luck@gmail.com","sentAt":"2005-10-01T04:40:23Z","receivedAt":"2005-10-01T04:40:23Z","isPatch":false,"sender":{"key":"tony.luck@gmail.com","avatar":null},"body":"I see that Linus made a new incremental pack when he\nreleased 2.6.14-rc3 ... so to be nice to the kernel.org\nmirroring daemons I should make use of them.\n\nAfter the excitement I had last time with packs and trying to\nmake use of alternate directories, I thought I'd check the\nprocess before I touched anything.\n\n1) Link the new pack files from Linus' objects/pack directory\nto my objects/pack directory.\n\n2) $ GIT_DIR=. git prune-packed # in my directory\n\n3) $ GIT_DIR=. git update-server-info # ditto\n\nOk?\n\n-Tony\n"},{"id":"9585","messageId":"7vacht902k.fsf@assigned-by-dhcp.cox.net","threadId":"1988","inReplyTo":"12c511ca0509302140o4263020bsc337594609175173@mail.gmail.com","subject":"Re: time to update with new packs","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-10-01T07:18:59Z","receivedAt":"2005-10-01T07:18:59Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Tony Luck <tony.luck@gmail.com> writes:\n\n> 1) Link the new pack files from Linus' objects/pack directory\n> to my objects/pack directory.\n>\n> 2) $ GIT_DIR=. git prune-packed # in my directory\n>\n> 3) $ GIT_DIR=. git update-server-info # ditto\n\nWhen everybody uses more recent clients, you could say\n\"/pub/scm/.../torvalds/linux-2.6.git/objects\" in your\nobjects/info/alternates file and not worry about step (1).  git\nnative transport has known about the alternate mechanism since\nthe inception.  The alternate mechanism support in \"git fetch\"\nand \"git clone\" for rsync and http transports is a relatively\nrecent addition (appeared just before 0.99.7).\n\nSo (1) is not necessary for git native transport once you have\n\"alternate\" file, but for other transports (1) is probably still\nhelpful at this point.\n\nAlso, enabling hooks/post-update in your public repository would\nsave you from worrying about (3), provided if the only way you\nupdate it is by pushing into it, which I think is what usually\npeople are doing.\n"}]}