git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Building Git with HTTPS support: avoiding libcurl?

From
Paul Smith <paul@mad-scientist.net>
Date
Dec 22, 2015, 17:30 UTC
Message-ID
<1450805416.11255.58.camel@mad-scientist.net>
In-Reply-To
<CAD0k6qT+s4e_7y1DxVTN63V0tO_xFv-9i-Fmq5O0SrpQAyAzVA@mail.gmail.com>
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 :).

Previous: Dave BorowitzNext: Daniel Stenberg
Message 3 of 6 in “Building Git with HTTPS support: avoiding libcurl?”
  1. Paul SmithDec 22, 2015
  2. Dave BorowitzDec 22, 2015
  3. Paul SmithDec 22, 2015
  4. Daniel StenbergDec 23, 2015
  5. Johannes SchindelinDec 23, 2015
  6. Thiago FarinaDec 24, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.