All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Faye-Lund <kusmabite@gmail.com>
To: Dave Borowitz <dborowitz@google.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Marat Radchenko <marat@slonopotamus.org>,
	 msysGit <msysgit@googlegroups.com>,
	Pat Thoyts <patthoyts@gmail.com>,
	 Nick Hengeveld <nickh@reactrix.com>,
	GIT Mailing-list <git@vger.kernel.org>
Subject: Re: git version 1.9.0 missing git-http-push?
Date: Mon, 28 Apr 2014 21:02:19 +0200	[thread overview]
Message-ID: <CABPQNSaOVrUJVQcE8pyfohP4tgvD+bRPScw-igsFj08H3EoRWA@mail.gmail.com> (raw)
In-Reply-To: <CAD0k6qSUYANxbjjbE4jTW4EeVwOYgBD=bXkSu=akiYC_CB7Ffw@mail.gmail.com>

On Mon, Apr 28, 2014 at 8:39 PM, Dave Borowitz <dborowitz@google.com> wrote:
> On Mon, Apr 28, 2014 at 11:31 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> Erik Faye-Lund <kusmabite@gmail.com> writes:
>>
>>> We're using Curl 7.30.0 in msysGit (and thus also Git for Windows), so
>>> we should be able to include it. However, we do not have curl-config
>>> installed.
>>
>> Hmmm, between 2.0-rc0 and 2.0-rc1 there is 61a64fff (Makefile: use
>> curl-config to determine curl flags, 2014-04-15) merged already,
>> which makes this assumption and a claim based on that assumption:
>>
>>     curl-config should always be installed alongside a curl
>>     distribution, and its purpose is to provide flags for building
>>     against libcurl, so use it instead of guessing flags and
>>     dependent libraries.
>>
>> which may make things worse for you guys, unless you are explicitly
>> setting CURLDIR and other Makefile variables.
>
> Yes, I can see that assumption may not always hold. But I'm slightly
> surprised this worked in the first place; are you saying this is a
> system where:
> -curl-config is not installed
> -but -lcurl still works
> -without setting CURLDIR
> ?

Yes, our cURL is installed globally together with the system libraries.

> I think I should probably re-roll the patch to default to the old
> behavior (blind -lcurl) if curl-config returns the empty string, which
> I believe is also the case when the binary is not found.

That sounds like it would work for MsysGit, yeah.

-- 
-- 
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.

You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en

--- 
You received this message because you are subscribed to the Google Groups "msysGit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

  reply	other threads:[~2014-04-28 19:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28  6:19 git version 1.9.0 missing git-http-push? Silvola Tuomas
2014-04-28  7:36 ` Marat Radchenko
2014-04-28  8:48   ` Erik Faye-Lund
2014-04-28  9:01     ` Erik Faye-Lund
2014-04-28  9:43       ` Erik Faye-Lund
2014-04-28 13:12       ` Erik Faye-Lund
2014-04-28 13:20       ` Johannes Schindelin
2014-04-28 13:24         ` Erik Faye-Lund
2014-04-28 13:47         ` Marat Radchenko
2014-04-28 13:53           ` Erik Faye-Lund
2014-04-28 18:31     ` Junio C Hamano
2014-04-28 18:39       ` 'Dave Borowitz <dborowitz@google.com>' via msysGit
2014-04-28 19:02         ` Erik Faye-Lund [this message]
2014-04-28 19:40         ` Junio C Hamano
2014-04-28 19:42           ` 'Dave Borowitz <dborowitz@google.com>' via msysGit

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=CABPQNSaOVrUJVQcE8pyfohP4tgvD+bRPScw-igsFj08H3EoRWA@mail.gmail.com \
    --to=kusmabite@gmail.com \
    --cc=dborowitz@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=marat@slonopotamus.org \
    --cc=msysgit@googlegroups.com \
    --cc=nickh@reactrix.com \
    --cc=patthoyts@gmail.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 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.