From: "Torsten Bögershausen" <tboegi@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Torsten Bögershausen" <tboegi@web.de>,
"Jeff King" <peff@peff.net>,
"Mark Levedahl" <mlevedahl@gmail.com>,
git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2012, #03; Tue, 13)
Date: Sat, 17 Nov 2012 08:11:24 +0100 [thread overview]
Message-ID: <50A7389C.6080003@web.de> (raw)
In-Reply-To: <7vlie1mlcb.fsf@alter.siamese.dyndns.org>
On 16.11.12 19:52, Junio C Hamano wrote:
> Torsten Bögershausen <tboegi@web.de> writes:
>
>> My understanding:
>> Either use people cygwin 1.5 or they use cygwin 1.7, and in this case
>> the installation is updated frequently.
>>
>> Peff or Junio, please go ahead with the patch.
>>
>> If it turns out that we want to support cygwin installations like 1.7.7
>> which could be upgraded, but are not upgraded since they are
>> "production machines we do not dare to touch" we can still improve
>> the autodetection.
>
> OK. I moved the topic forward but we may still want to rename the
> name of the macro to have CYGWIN somewhere in the name.
I send a patch some seconds ago.
I forgot to mention that this should be applied to next
next prev parent reply other threads:[~2012-11-17 7:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 17:52 What's cooking in git.git (Nov 2012, #03; Tue, 13) Jeff King
2012-11-13 20:01 ` Junio C Hamano
2012-11-13 20:45 ` Torsten Bögershausen
2012-11-13 20:48 ` Pyeron, Jason J CTR (US)
2012-11-14 1:18 ` Mark Levedahl
2012-11-14 19:02 ` Jeff King
2012-11-14 21:13 ` Torsten Bögershausen
2012-11-15 0:16 ` Jeff King
2012-11-15 0:19 ` Junio C Hamano
2012-11-15 1:50 ` Mark Levedahl
2012-11-15 1:56 ` Jeff King
2012-11-15 5:54 ` Torsten Bögershausen
2012-11-16 18:52 ` Junio C Hamano
2012-11-17 7:11 ` Torsten Bögershausen [this message]
2012-11-15 19:05 ` Ramsay Jones
2012-11-15 19:35 ` Torsten Bögershausen
2012-11-15 23:34 ` Mark Levedahl
2012-11-13 22:57 ` Junio C Hamano
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=50A7389C.6080003@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mlevedahl@gmail.com \
--cc=peff@peff.net \
/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).