On Fri, 4 May 2012, Jeff King wrote:
I don't see any way around it besides implementing curl's full tokenizing and matching algorithm, which is about a page of code. I'd really prefer not to re-implement bits of curl (especially because they may change later), but AFAIK there is no way to ask curl "is there a proxy configured, and if so, what is it?".
Sorry for being thick, but I lost track on this thread. Why does it need this info again?
Or perhaps put another way: if there was an ideal way to get this done or provide this to libcurl other than the current way, how would you suggest it would be done from a git internal point of view?
We're currently discussing new ways of providing authentication info in libcurl and I want to make sure I can get useful bits from this exercise into that talk to possibly offer something smoother in the future.
-- / daniel.haxx.se -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html