git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Schuberth <sschuberth@gmail.com>
To: Erik Faye-Lund <kusmabite@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Junio C Hamano <gitster@pobox.com>,
	Dave Borowitz <dborowitz@google.com>,
	GIT Mailing-list <git@vger.kernel.org>,
	Pat Thoyts <patthoyts@gmail.com>,
	Marat Radchenko <marat@slonopotamus.org>,
	tuomas.silvola@knowit.fi, msysGit <msysgit@googlegroups.com>
Subject: Re: [PATCH/RFC] Makefile: do not depend on curl-config
Date: Mon, 5 May 2014 12:56:20 +0200	[thread overview]
Message-ID: <CAHGBnuMTc8MuUd9_BtqkemJ--_fxmRroc0pym78hDF=Jc7KPLw@mail.gmail.com> (raw)
In-Reply-To: <CABPQNSb83H7EEeAfaxC7KVpZmv-KEqE1wavTf53kA=aoDQz4Tw@mail.gmail.com>

On Mon, May 5, 2014 at 12:53 PM, Erik Faye-Lund <kusmabite@gmail.com> wrote:

>>> FWIW the plan is to switch to mingwGitDevEnv for the 2.0 release. It is
>>> not quite clear as of yet how patches will be managed with said
>>> environment.
>>
>> The environment is just that: The environment to build Git for
>> Windows. This means that patches on top of Git for Windows could still
>> be maintained in msysgit/git (or a fork thereof) on GitHub.
>
> Thanks for the heads up. Even so, are you guys OK with me pushing this
> patch to our downstream repo?

Fine with me.

-- 
Sebastian Schuberth

  reply	other threads:[~2014-05-06 16:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28 16:29 [PATCH/RFC] Makefile: do not depend on curl-config Erik Faye-Lund
2014-04-30 13:08 ` Erik Faye-Lund
2014-04-30 15:27 ` Junio C Hamano
2014-04-30 15:29   ` 'Dave Borowitz' via msysGit
2014-04-30 15:53   ` Erik Faye-Lund
2014-04-30 16:52     ` Johannes Schindelin
2014-04-30 19:46       ` Sebastian Schuberth
2014-05-05 10:53         ` Erik Faye-Lund
2014-05-05 10:56           ` Sebastian Schuberth [this message]
2014-05-05 15:03           ` [msysGit] " Thomas Braun

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='CAHGBnuMTc8MuUd9_BtqkemJ--_fxmRroc0pym78hDF=Jc7KPLw@mail.gmail.com' \
    --to=sschuberth@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=dborowitz@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kusmabite@gmail.com \
    --cc=marat@slonopotamus.org \
    --cc=msysgit@googlegroups.com \
    --cc=patthoyts@gmail.com \
    --cc=tuomas.silvola@knowit.fi \
    /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;
as well as URLs for NNTP newsgroup(s).