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

Re: Building Git with HTTPS support: avoiding libcurl?

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 23, 2015, 19:35 UTC
Message-ID
<alpine.DEB.2.20.1512232033170.14434@virtualbox>
In-Reply-To
<alpine.DEB.2.11.1512231059380.23702@tvnag.unkk.fr>
Hi Daniel,
On Wed, 23 Dec 2015, Daniel Stenberg wrote:
> By re-using a very widely used, well developed and properly documented
> library [libcurl] (yeah, I claim it is but you don't need to take my
> word for it) that is available everywhere - git benefits.

For what it's worth, I fully agree. My perspective: By using a pretty much fully-configured cURL, Git for Windows has supported the largest number of use cases with minimal requirements from myself. It has been a boon. If every library was as easy to use and as high quality, anybody could maintain Git for Windows ;-)

Ciao, a very grateful Dscho

Previous: Daniel StenbergNext: Thiago Farina
Message 5 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.