{"thread":{"id":"7569","subject":"[PATCH 0/8] git-repack --max-pack-size","startedAt":"2007-04-08T23:17:40Z","lastAt":"2007-04-09T19:43:52Z","messageCount":4,"participants":["Dana How","Nicolas Pitre"],"isPatch":true,"patchVersion":1,"patchTotal":8},"messages":[{"id":"38887","messageId":"46197814.5010909@gmail.com","threadId":"7569","inReplyTo":null,"subject":"[PATCH 0/8] git-repack --max-pack-size","fromName":"Dana How","fromEmail":"danahow@gmail.com","sentAt":"2007-04-08T23:17:40Z","receivedAt":"2007-04-08T23:17:40Z","isPatch":true,"sender":{"key":"danahow@gmail.com","avatar":null},"body":"\nThe three most common ways of making large packfiles\nare git-fast-import, the first git-repack, or git-repack -a.\nThe first already supports a \"--max-pack-size=N\" option,\nwhich limits the resulting packfiles to N megabytes.\nThis patchset adds the same option, with the same\nbehavior, to git-repack to handle the other two cases.\n\nAfter reviewing others' comments,  this latest patchset\ntouches 2/3 fewer files and 1/6 fewer lines,  and\nintroduces no behavior not seen elsewhere in git.\n"},{"id":"38904","messageId":"alpine.LFD.0.98.0704082229290.28181@xanadu.home","threadId":"7569","inReplyTo":"46197814.5010909@gmail.com","subject":"Re: [PATCH 0/8] git-repack --max-pack-size","fromName":"Nicolas Pitre","fromEmail":"nico@cam.org","sentAt":"2007-04-09T02:33:53Z","receivedAt":"2007-04-09T02:33:53Z","isPatch":true,"sender":{"key":"nico@fluxnic.net","avatar":"https://avatars.githubusercontent.com/u/702790?v=4"},"body":"On Sun, 8 Apr 2007, Dana How wrote:\n\n> After reviewing others' comments,  this latest patchset\n> touches 2/3 fewer files and 1/6 fewer lines,  and\n> introduces no behavior not seen elsewhere in git.\n\nI'm starting to like it, but...\n\nI have some extensive changes that touch the same area more or less.  \nAnd so far I think it might be easier to rebase your changes on top of \nmine rather than the other way around.\n\nSo I'd like if my changes would be merged first and then yours to be \napplied afterwards.  They still have some issues left anyway.\n\nI'm trying to format my changes now and send them tonight.\n\n\nNicolas\n"},{"id":"38962","messageId":"56b7f5510704091154o2a52d563p1c0c72519447a1eb@mail.gmail.com","threadId":"7569","inReplyTo":"alpine.LFD.0.98.0704082229290.28181@xanadu.home","subject":"Re: [PATCH 0/8] git-repack --max-pack-size","fromName":"Dana How","fromEmail":"danahow@gmail.com","sentAt":"2007-04-09T18:54:17Z","receivedAt":"2007-04-09T18:54:17Z","isPatch":true,"sender":{"key":"danahow@gmail.com","avatar":null},"body":"On 4/8/07, Nicolas Pitre <nico@cam.org> wrote:\n> On Sun, 8 Apr 2007, Dana How wrote:\n>\n> > After reviewing others' comments,  this latest patchset\n> > touches 2/3 fewer files and 1/6 fewer lines,  and\n> > introduces no behavior not seen elsewhere in git.\n>\n> I'm starting to like it, but...\n>\n> I have some extensive changes that touch the same area more or less.\n> And so far I think it might be easier to rebase your changes on top of\n> mine rather than the other way around.\n>\n> So I'd like if my changes would be merged first and then yours to be\n> applied afterwards.  They still have some issues left anyway.\n>\n> I'm trying to format my changes now and send them tonight.\nThanks for sending them out.\nI guess I'll update mine to apply after yours once\nyours show up in the appropriate branch.\n\nThanks,\n-- \nDana L. How  danahow@gmail.com  +1 650 804 5991 cell\n"},{"id":"38968","messageId":"56b7f5510704091243w2ef54809m339663b3fbf72ad6@mail.gmail.com","threadId":"7569","inReplyTo":"46197814.5010909@gmail.com","subject":"Re: [PATCH 0/8] git-repack --max-pack-size","fromName":"Dana How","fromEmail":"danahow@gmail.com","sentAt":"2007-04-09T19:43:52Z","receivedAt":"2007-04-09T19:43:52Z","isPatch":true,"sender":{"key":"danahow@gmail.com","avatar":null},"body":"On 4/8/07, Dana How <danahow@gmail.com> wrote:\n> The three most common ways of making large packfiles\n> are git-fast-import, the first git-repack, or git-repack -a.\n> The first already supports a \"--max-pack-size=N\" option,\n> which limits the resulting packfiles to N megabytes.\n> This patchset adds the same option, with the same\n> behavior, to git-repack to handle the other two cases.\n>\n> After reviewing others' comments,  this latest patchset\n> touches 2/3 fewer files and 1/6 fewer lines,  and\n> introduces no behavior not seen elsewhere in git.\n\nAt the moment,  I plan the following changes to this patchset:\n* Redo after 64b index applied (Nicolas)\n* Bad re-use of header around sha1write (Nicolas)\n* Set object_entry.offset before write_object (Dana)\n* Finish reducing struct object_entry (Junio)\n* Remove spaces from inside () (Junio)\n\nConcerning refactorings,\nI'd prefer to keep those in a separate (follow-on?) patchset.\n\nThanks,\n-- \nDana L. How  danahow@gmail.com  +1 650 804 5991 cell\n"}]}