From: Paul Smith <paul@mad-scientist.net>
To: git <git@vger.kernel.org>
Subject: Re: Building Git with HTTPS support: avoiding libcurl?
Date: Tue, 22 Dec 2015 12:30:16 -0500 [thread overview]
Message-ID: <1450805416.11255.58.camel@mad-scientist.net> (raw)
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 :).
next prev parent reply other threads:[~2015-12-22 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 15:39 Building Git with HTTPS support: avoiding libcurl? Paul Smith
2015-12-22 17:08 ` Dave Borowitz
2015-12-22 17:30 ` Paul Smith [this message]
2015-12-23 10:17 ` Daniel Stenberg
2015-12-23 19:35 ` Johannes Schindelin
2015-12-24 22:36 ` Thiago Farina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1450805416.11255.58.camel@mad-scientist.net \
--to=paul@mad-scientist.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).