{"thread":{"id":"32897","subject":"Recommended packing for HTTP repositories","startedAt":"2013-02-13T12:38:42Z","lastAt":"2013-02-13T12:38:42Z","messageCount":1,"participants":["Robert Clausecker"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"209465","messageId":"1360759122.6610.15.camel@t520","threadId":"32897","inReplyTo":null,"subject":"Recommended packing for HTTP repositories","fromName":"Robert Clausecker","fromEmail":"fuzxxl@gmail.com","sentAt":"2013-02-13T12:38:42Z","receivedAt":"2013-02-13T12:38:42Z","isPatch":false,"sender":{"key":"fuzxxl@gmail.com","avatar":"https://gravatar.com/avatar/4e7ce39f11fdb27adbc2f3ed63d580cd0f69958a94ef04381f4aad53ed083909?d=mp&s=160"},"body":"Hello!\n\nI provide dumb HTTP access to a git repository on a server where I can't\nenable the smart HTTP protocol. When the history of the repository\ngrows, should I run git repack to pack all revisions together? Would\nthat cause clients that just want to download a few commit to download\nthe whole pack? What is recommended to do?\n\nYours, Robert Clausecker\n"}]}