{"thread":{"id":"8992","subject":"[PATCH 0/4] The rest of builtin-fetch","startedAt":"2007-07-12T01:36:57Z","lastAt":"2007-07-12T01:49:01Z","messageCount":3,"participants":["Daniel Barkalow","Johannes Schindelin"],"isPatch":true,"patchVersion":1,"patchTotal":4},"messages":[{"id":"47100","messageId":"Pine.LNX.4.64.0707112113460.6977@iabervon.org","threadId":"8992","inReplyTo":null,"subject":"[PATCH 0/4] The rest of builtin-fetch","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2007-07-12T01:36:57Z","receivedAt":"2007-07-12T01:36:57Z","isPatch":true,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"This series is the rest of builtin-fetch. It should probably not be used \nwithout a \"[PATCH 3.5/4] Support bundles in transport fetch\" which \nJohannes was going to write.\n\nThe first patch of this is independant of anything else, but the rest \ndepend on all of the other series I have sent recently. One thing I \nalready plan to fix while doing revisions for comments is that the \n\"remote.<name>.tagopt\" config variable parsing is added by the second \npatch, when it would be more logically added by the first.\n\nWhen the development cycle is at the right point for getting all this in, \nI'll be sending out the complete set of patches (aside from the pair that \nwere already accepted). I'm also going to send out another revision of \nbuiltin-fetch-pack.c that adds a bit of memory freeing and depends on the \nfirst of the accepted pair. And I've got a builtin-send-pack (with a \nfunction for transport.c to call directly), although that's not in the \ncritical path.\n\n\t-Daniel\n*This .sig left intentionally blank*\n"},{"id":"47105","messageId":"Pine.LNX.4.64.0707120244200.4516@racer.site","threadId":"8992","inReplyTo":"Pine.LNX.4.64.0707112113460.6977@iabervon.org","subject":"Re: [PATCH 0/4] The rest of builtin-fetch","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-07-12T01:44:36Z","receivedAt":"2007-07-12T01:44:36Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Wed, 11 Jul 2007, Daniel Barkalow wrote:\n\n> This series is the rest of builtin-fetch. It should probably not be used \n> without a \"[PATCH 3.5/4] Support bundles in transport fetch\" which \n> Johannes was going to write.\n\n8-)\n\nIt is 3am, and I am already in the middle of git hacking, and should go to \nbed, so that'll have to wait for tomorrow...\n\nCiao,\nDscho\n"},{"id":"47106","messageId":"Pine.LNX.4.64.0707112145220.6977@iabervon.org","threadId":"8992","inReplyTo":"Pine.LNX.4.64.0707120244200.4516@racer.site","subject":"Re: [PATCH 0/4] The rest of builtin-fetch","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2007-07-12T01:49:01Z","receivedAt":"2007-07-12T01:49:01Z","isPatch":true,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"On Thu, 12 Jul 2007, Johannes Schindelin wrote:\n\n> Hi,\n> \n> On Wed, 11 Jul 2007, Daniel Barkalow wrote:\n> \n> > This series is the rest of builtin-fetch. It should probably not be used \n> > without a \"[PATCH 3.5/4] Support bundles in transport fetch\" which \n> > Johannes was going to write.\n> \n> 8-)\n> \n> It is 3am, and I am already in the middle of git hacking, and should go to \n> bed, so that'll have to wait for tomorrow...\n\nWe're presumably waiting for 1.5.3 before this actually goes anywhere, so \nthere's no big hurry. Just don't want it to get forgotten and have \nmainline versions where the tests don't pass due to bundles not working \n(or, worse, an actual release where we forget about them in this context).\n\n\t-Daniel\n*This .sig left intentionally blank*\n"}]}