From: Nick Hengeveld <nickh@reactrix.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Some curl versions lack curl_easy_duphandle()
Date: Mon, 17 Oct 2005 11:01:30 -0700 [thread overview]
Message-ID: <20051017180130.GJ5509@reactrix.com> (raw)
In-Reply-To: <20051016215018.GG5509@reactrix.com>
On Sun, Oct 16, 2005 at 02:50:18PM -0700, Nick Hengeveld wrote:
> Is that the correct version number? I've been using 7.10.6 and
> curl_easy_duphandle() has been working fine.
Apart from the version number question, this patch looks good. Although
I'm now wondering whether it makes sense to bother trying to use
curl_easy_duphandle() at all and always use get_curl_handle() instead.
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
next prev parent reply other threads:[~2005-10-17 18:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 22:39 [PATCH] Some curl versions lack curl_easy_duphandle() Johannes Schindelin
2005-10-15 5:49 ` Junio C Hamano
2005-10-15 11:50 ` Johannes Schindelin
2005-10-16 21:50 ` Nick Hengeveld
2005-10-16 21:58 ` Johannes Schindelin
2005-10-17 18:01 ` Nick Hengeveld [this message]
2005-10-17 18:54 ` Johannes Schindelin
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=20051017180130.GJ5509@reactrix.com \
--to=nickh@reactrix.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.