git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: J Smith <dark.panda@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFC] grep: add a grep.patternType configuration setting
Date: Fri, 3 Aug 2012 14:22:49 -0400	[thread overview]
Message-ID: <CADFUPge8LdBKHFrs32gFtzFwvvbK6OSxfMBdHF6fyRwtcCocTw@mail.gmail.com> (raw)
In-Reply-To: <7vsjc4aq0b.fsf@alter.siamese.dyndns.org>

On Fri, Aug 3, 2012 at 12:39 PM, Junio C Hamano <gitster@pobox.com> wrote:
>
> Much nicer than the drafts in earlier discussion.  One micronit is
> that probably it is preferrable to do '!=' instead of '>', as we are
> only trying to see if it is unspecified on the command line (hence
> need to pay attention to configuration) and do not care how the
> enums are ordered, but that is nothing that requires a re-roll.

True enough. Old habits I guess, eh?

> All the new tests in the script looked very well thought out.
>
> I noticed that this particular one will still succeed when somebody
> breaks your code to ignore the configuration (as -G "a+b" would give
> the expected match) or give higher precedence to the configuration
> (as fixed "a+b" also will give the expected match).  Not that it is
> wrong to have such a test that is unlikely to catch certain kinds of
> regressions in the suite, and the particular kind of breakage will
> be caught by the next test (snipped) anyway.

Yeah, that test is kind of iffy, but does no harm I suppose.

> Will queue.  Thanks.

Great, thanks. Been an informative experience for a first-time git
patcher. Cheers.

  reply	other threads:[~2012-08-03 18:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03 14:53 [PATCH/RFC] grep: add a grep.patternType configuration setting J Smith
2012-08-03 16:39 ` Junio C Hamano
2012-08-03 18:22   ` J Smith [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-08-01 18:29 J Smith
2012-08-01 21:55 ` Junio C Hamano
2012-08-01 22:19   ` Štěpán Němec
2012-08-01 22:49   ` J Smith
2012-08-02 14:47     ` J Smith

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=CADFUPge8LdBKHFrs32gFtzFwvvbK6OSxfMBdHF6fyRwtcCocTw@mail.gmail.com \
    --to=dark.panda@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).