From: arjen@yaph.org (Arjen Laarhoven)
To: Pieter de Bie <pieter@frim.nl>
Cc: Brandon Casey <casey@nrlssc.navy.mil>, Jeff King <peff@peff.net>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>,
Mike Ralphson <mike@abacus.co.uk>
Subject: Re: What's in git.git (Oct 2008, #03; Tue, 14)
Date: Fri, 17 Oct 2008 09:02:45 +0200 [thread overview]
Message-ID: <20081017070245.GA29345@regex.yaph.org> (raw)
In-Reply-To: <465E8DD6-CBDC-4E02-9C7F-57CBE81E3549@frim.nl>
On Thu, Oct 16, 2008 at 05:37:10PM +0200, Pieter de Bie wrote:
>
> On 16 okt 2008, at 17:21, Brandon Casey wrote:
>
> >Darwin, anyone?
>
> 'maint' passes for me on Darwin (OS X Leopard) after removing the
> regex stuff in Makefile
Yup, confirmed.
Arjen
--
Arjen Laarhoven
The presence of those seeking the truth is infinitely to be preferred to
those who think they've found it.
-- Terry Pratchett, "Monstrous Regiment"
next prev parent reply other threads:[~2008-10-17 7:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 22:08 What's in git.git (Oct 2008, #03; Tue, 14) Junio C Hamano
2008-10-15 15:35 ` Brandon Casey
2008-10-15 17:25 ` Mike Ralphson
2008-10-15 19:38 ` Junio C Hamano
2008-10-15 20:20 ` Shawn O. Pearce
2008-10-15 20:26 ` Junio C Hamano
2008-10-15 20:36 ` Shawn O. Pearce
2008-10-16 0:58 ` [PATCH maint 1/2] t4018-diff-funcname: rework negated last expression test drafnel
[not found] ` <1224118730-24711-1-git-send-email-drafnel@gmail.com>
2008-10-16 0:58 ` [PATCH maint 2/2] t4018-diff-funcname: demonstrate end of line funcname matching flaw drafnel
2008-10-16 10:08 ` What's in git.git (Oct 2008, #03; Tue, 14) Jeff King
2008-10-16 15:21 ` Brandon Casey
2008-10-16 15:37 ` Pieter de Bie
2008-10-17 7:02 ` Arjen Laarhoven [this message]
2008-10-24 2:44 ` Junio C Hamano
2008-10-17 9:53 ` Jeff King
2008-10-17 23:58 ` 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=20081017070245.GA29345@regex.yaph.org \
--to=arjen@yaph.org \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mike@abacus.co.uk \
--cc=peff@peff.net \
--cc=pieter@frim.nl \
--cc=spearce@spearce.org \
/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.