From: Jeff King <peff@peff.net>
To: Brandon Casey <casey@nrlssc.navy.mil>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Arjen Laarhoven <arjen@yaph.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: Thu, 16 Oct 2008 06:08:05 -0400 [thread overview]
Message-ID: <20081016100805.GA20762@sigill.intra.peff.net> (raw)
In-Reply-To: <bsftmRx17krWBpVlulipoJEO1fWsD0hZfF3HOZcajX6GV66RKW8W6A@cipher.nrlssc.navy.mil>
On Wed, Oct 15, 2008 at 10:35:30AM -0500, Brandon Casey wrote:
> 2) Do we want to stick with compat/regex on
>
> Darwin: Arjen
> FreeBSD: Jeff
> AIX: Mike
>
> now that the builtin funcname patterns have been converted to Extended
> Regular Expressions?
t4018 passes without compat/regex on FreeBSD. Is that a sufficient test?
-Peff
next prev parent reply other threads:[~2008-10-16 10:09 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 ` Jeff King [this message]
2008-10-16 15:21 ` What's in git.git (Oct 2008, #03; Tue, 14) Brandon Casey
2008-10-16 15:37 ` Pieter de Bie
2008-10-17 7:02 ` Arjen Laarhoven
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=20081016100805.GA20762@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=arjen@yaph.org \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mike@abacus.co.uk \
--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 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).