public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: Dave Borowitz <dborowitz@google•com>
Cc: kusmabite@gmail•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 12:40:06 -0700	[thread overview]
Message-ID: <xmqqy4ypp7jd.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAD0k6qSUYANxbjjbE4jTW4EeVwOYgBD=bXkSu=akiYC_CB7Ffw@mail.gmail.com> (via msysGit's message of "Mon, 28 Apr 2014 11:39:43 -0700")

"'Dave Borowitz <dborowitz@google•com>' via msysGit"
<msysgit@googlegroups•com> writes:

> 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.

Thanks for a prompt response; as this may indicate a possible
regression on what is already in 2.0-rc1, I am tempted to say that
we should revert the merge in the meantime.

Unless such an update can be done in a fairly trivial way, that is.


-- 
-- 
*** 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.

  parent reply	other threads:[~2014-04-28 19:40 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
2014-04-28 19:40         ` Junio C Hamano [this message]
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=xmqqy4ypp7jd.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=dborowitz@google$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=kusmabite@gmail$(echo .)com \
    --cc=marat@slonopotamus$(echo .)org \
    --cc=msysgit@googlegroups$(echo .)com \
    --cc=nickh@reactrix$(echo .)com \
    --cc=patthoyts@gmail$(echo .)com \
    /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