All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: js/gcc-8-and-9, was Re: What's cooking in git.git (Jun 2019, #04; Fri, 14)
Date: Wed, 19 Jun 2019 07:28:00 -0700	[thread overview]
Message-ID: <xmqqsgs5r6of.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1906181221360.44@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Tue, 18 Jun 2019 12:26:06 +0200 (CEST)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> What I *tried* to suggest is to take my minimal `kwset: allow building
> with GCC 8` together with the other three, as it fixes the build. Without
> it, the build is not fixed under `DEVELOPER=1`, it is still broken.

Ah, of course, we can do that.  

Whether we are going to replace with newer LGPL2.1 copy (which I
think is more conservative and tend to prefer) or removing it and
require PCREv2 from everybody who does not want to see their
fixed-grep performance degraded, we won't keep the "hack" when we
take the one of these solutions for longer term, but it is a minimal
and obvious workaround.

  reply	other threads:[~2019-06-19 14:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14 20:50 What's cooking in git.git (Jun 2019, #04; Fri, 14) Junio C Hamano
2019-06-17 17:41 ` js/gcc-8-and-9, was " Johannes Schindelin
2019-06-17 19:54   ` Junio C Hamano
2019-06-18 10:26     ` Johannes Schindelin
2019-06-19 14:28       ` Junio C Hamano [this message]
2019-06-17 18:06 ` pw/rebase-abort-clean-rewritten, " Johannes Schindelin
2019-06-17 19:04   ` Phillip Wood
2019-06-18  3:30     ` Junio C Hamano
2019-06-20  9:34       ` Phillip Wood
2019-06-21 13:27         ` Johannes Schindelin
2019-06-17 18:25 ` sg/rebase-progress, " Johannes Schindelin
2019-06-18 13:36 ` ds/commit-graph-incremental (was Re: What's cooking in git.git (Jun 2019, #04; Fri, 14)) Derrick Stolee
2019-06-19 14:32   ` Junio C Hamano
2019-06-19 14:37     ` Derrick Stolee

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=xmqqsgs5r6of.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.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.