From: Paul Smith Date: Tue, 22 Dec 2015 17:30:16 GMT Subject: Re: Building Git with HTTPS support: avoiding libcurl? Message-ID: <1450805416.11255.58.camel@mad-scientist.net> In-Reply-To: On Tue, 2015-12-22 at 09:08 -0800, Dave Borowitz wrote: > Well, IIUC one of the reasons for Git's fork-everything strategy is to > avoid having to dynamically link the core git binary against large > libraries like libcurl, so the dependency size has been taken into > account at least in that sense. Sure, and it's great that I still get most Git even if I don't have libcurl. But without support for cloning https remotes there's a significant hole in Git functionality... I grok that Git doesn't want to re-invent the wheel and that libcurl is convenient. I just wonder if anyone knows of another wheel, that doesn't come attached to an entire tractor-trailer, that could be used instead :).