All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeffrey Walton <noloader@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Git and PCRE2 vs PCRE?
Date: Thu, 30 Mar 2017 18:04:23 -0400	[thread overview]
Message-ID: <CAH8yC8kEzK0seNj9GK8h5mnMDvyG9=PnChmseSuvSfvb5h+uDQ@mail.gmail.com> (raw)
In-Reply-To: <xmqq60iq31dk.fsf@gitster.mtv.corp.google.com>

On Thu, Mar 30, 2017 at 5:23 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Jeffrey Walton <noloader@gmail.com> writes:
>
>> Is it possible to use PCRE2 with Git? If so, how do I tell Git to use PCRE2?
>
> Given that pcre2's symbols are all prefixed with pcre2_ (I only
> checked http://www.pcre.org/current/doc/html/pcre2api.html) and we
> do not see any hits from "git grep pcre2", I do not think you can
> just "configure" Git to use it.  Unless pcre2 library has a drop-in
> replacement backward compatibility mode with pcre library, that is.
>
> It probably is possible to use PCRE2 with Git by adding similar
> amount of code to grep.[ch] as we have support for pcre and that
> would be the way you tell Git to use PCRE2, but I think that is
> probably not the questino you are asking.

Ack, thanks Jeff and Junio. Its no big deal to me.

I'm not a PCRE user, so I'm not familiar with the extra gyrations
needed for the migration.

I'll get the original PCRE installed.

Thanks again.

      reply	other threads:[~2017-03-30 22:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 20:59 Git and PCRE2 vs PCRE? Jeffrey Walton
2017-03-30 21:22 ` Jeff King
2017-03-30 21:23 ` Junio C Hamano
2017-03-30 22:04   ` Jeffrey Walton [this message]

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='CAH8yC8kEzK0seNj9GK8h5mnMDvyG9=PnChmseSuvSfvb5h+uDQ@mail.gmail.com' \
    --to=noloader@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 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.