{"thread":{"id":"9099","subject":"USE_CURL_MULTI and http.h in general","startedAt":"2007-07-18T21:19:14Z","lastAt":"2007-07-18T21:19:14Z","messageCount":1,"participants":["Daniel Barkalow"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"47771","messageId":"Pine.LNX.4.64.0707181711450.14596@iabervon.org","threadId":"9099","inReplyTo":null,"subject":"USE_CURL_MULTI and http.h in general","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2007-07-18T21:19:14Z","receivedAt":"2007-07-18T21:19:14Z","isPatch":false,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"The changes I made to the commit-walker fetch code turn out not to work \nwith USE_CURL_MULTI, and I'm not at all clear on how to deal with it. I \nthink the current code for USE_CURL_MULTI also can't work for having \nmultiple things in the same executable using http.h, which will be a \nproblem for having both ls-remote and http-fetch as part of builtin-fetch, \nas well as eventually calling http-push without an exec from builtin-push. \nIs there anyone around who understands it?\n\n\t-Daniel\n*This .sig left intentionally blank*\n"}]}