From: Thomas Braun <thomas.braun@virtuell-zuhause.de>
To: kusmabite@gmail.com, Sebastian Schuberth <sschuberth@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: [msysGit] Re: [PATCH/RFC] Makefile: do not depend on curl-config
Date: Mon, 05 May 2014 17:03:27 +0200 [thread overview]
Message-ID: <5367A83F.5010606@virtuell-zuhause.de> (raw)
In-Reply-To: <CABPQNSb83H7EEeAfaxC7KVpZmv-KEqE1wavTf53kA=aoDQz4Tw@mail.gmail.com>
Am 05.05.2014 12:53, schrieb Erik Faye-Lund:
> On Wed, Apr 30, 2014 at 9:46 PM, Sebastian Schuberth
> <sschuberth@gmail.com> wrote:
>> On Wed, Apr 30, 2014 at 6:52 PM, Johannes Schindelin
>> <Johannes.Schindelin@gmx.de> wrote:
>>
>>>> We can keep this patch in the msysGit repo for the 2.0 release.
>>>
>>> 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?
Yes!
prev parent reply other threads:[~2014-05-06 16:17 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
2014-05-05 15:03 ` Thomas Braun [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=5367A83F.5010606@virtuell-zuhause.de \
--to=thomas.braun@virtuell-zuhause.de \
--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=sschuberth@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 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.