From: Junio C Hamano <gitster@pobox•com>
To: Remi Pommarel <repk@triplefau•lt>
Cc: Jonathan Nieder <jrnieder@gmail•com>,
git@vger•kernel.org, Brandon Casey <drafnel@gmail•com>,
Jeff King <peff@peff•net>
Subject: Re: [PATCH v3 1/1] Makefile: link libcurl before libssl
Date: Wed, 21 Oct 2015 09:52:05 -0700 [thread overview]
Message-ID: <xmqqy4ew5fm2.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20151021164406.GC13308@cruxbox> (Remi Pommarel's message of "Wed, 21 Oct 2015 18:44:06 +0200")
Remi Pommarel <repk@triplefau•lt> writes:
> On Tue, Oct 20, 2015 at 01:20:18PM -0700, Junio C Hamano wrote:
>>
>> So, what's the status of this patch and other two patches (I
>> consider them as a three-patch series)?
>
> So I have to fix the non initialized variable and to rephrase a litle
> bit the description for this patch. Taking libssl as an example is
> misleading, zlib is more appropriate. I'll resend another version shortly.
>
> For patch "[PATCH v3 1/1] Makefile: make curl-config path configurable"
> it has been reviewed by Jonathan Nieder with a litle modification to be
> squashed in. I can resend a squashed in version if it is easier for you.
Yes, please.
> Sorry for the delay.
No need to say sorry; people do their part at their own pace and
that is perfectly fine. I just wanted to make sure that some sign
of this topic not being forgotten would stay as I expunge older
messages from my mailbox ;-)
Thanks.
prev parent reply other threads:[~2015-10-21 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 19:24 [PATCH v3 1/1] Makefile: link libcurl before libssl Remi Pommarel
2015-10-05 19:41 ` Jonathan Nieder
2015-10-05 20:16 ` Remi Pommarel
2015-10-20 20:20 ` Junio C Hamano
2015-10-21 16:44 ` Remi Pommarel
2015-10-21 16:52 ` Junio C Hamano [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=xmqqy4ew5fm2.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=drafnel@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jrnieder@gmail$(echo .)com \
--cc=peff@peff$(echo .)net \
--cc=repk@triplefau$(echo .)lt \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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