From: Sverre Rabbelier <srabbelier@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Ramsay Jones <ramsay@ramsay1.demon.co.uk>,
Junio C Hamano <gitster@pobox.com>,
mstormo@gmail.com, GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH] Fix MSVC build on cygwin
Date: Thu, 8 Oct 2009 20:50:16 +0200 [thread overview]
Message-ID: <fabb9a1e0910081150s72d3b167k841175856c1f2b6f@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0910082040110.4985@pacific.mpi-cbg.de>
Heya,
On Thu, Oct 8, 2009 at 20:40, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> I thought we only used shell patterns for filenames, and regexes for
> everything else?
Maybe he's enacting a long silence after his Hi? "Hi "?
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-10-08 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 15:21 [PATCH] Fix MSVC build on cygwin Ramsay Jones
2009-10-08 18:40 ` Johannes Schindelin
2009-10-08 18:50 ` Sverre Rabbelier [this message]
2009-10-09 6:48 ` Junio C Hamano
2009-10-09 21:53 ` Ramsay Jones
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=fabb9a1e0910081150s72d3b167k841175856c1f2b6f@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mstormo@gmail.com \
--cc=ramsay@ramsay1.demon.co.uk \
/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).