From: Shawn Pearce <spearce@spearce.org>
To: Nick Hengeveld <nickh@reactrix.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-fetch: resolve remote symrefs for HTTP transport
Date: Wed, 26 Apr 2006 13:09:46 -0400 [thread overview]
Message-ID: <20060426170946.GA7843@spearce.org> (raw)
In-Reply-To: <20060426161001.GH32744@reactrix.com>
Nick Hengeveld <nickh@reactrix.com> wrote:
>
> Maybe this isn't the right way to handle this - since we're already
> calling perl we could use LWP to do the transfers (using keepalive
> even?)
LWP, no. My Mac OS X perl installation appears to have LWP installed
by dumb luck but my Gentoo Linux perl doesn't have LWP anywhere
in @INC. :-) Yet both systems run GIT happily.
The HTTP support in GIT is already linked against libcurl and libcurl
is required to use said HTTP support. I would think that libcurl
is capable of using Keep-Alive when possible, and libcurl and C
are certainly available anywhere GIT's HTTP support is currently
being used. Ideally any HTTP feature should either be using the
curl command line tool, or better, be written in C against the
libcurl library. But not LWP. Its not always available even though
a valid perl is.
--
Shawn.
prev parent reply other threads:[~2006-04-26 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 16:10 [PATCH] git-fetch: resolve remote symrefs for HTTP transport Nick Hengeveld
2006-04-26 17:09 ` Shawn Pearce [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060426170946.GA7843@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=nickh@reactrix.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox