git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/7] Update the compat/regex engine from upstream

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
May 8, 2017, 06:38 UTC
Message-ID
<CACBZZX4UzmFxDUwTA8JBX-UHDm4+c90qX7VmKqfDi+=783LmdQ@mail.gmail.com>
In-Reply-To
<xmqq8tm8cglo.fsf@gitster.mtv.corp.google.com>
On Mon, May 8, 2017 at 2:55 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 8 quoted lines
> Ævar Arnfjörð Bjarmason  <avarab@gmail.com> writes:
>
>> See the first patch for motivation & why.
>
> I do not think it quite explains the motivation, though.  "Doing
> this way, we can keep in sync with the upstream more easily"?  Or is
> there anything more to it, e.g. "and we need to update from the
> upstream now to fix this and that issues"?

It's just to bring us in line with upstream which as noted in that commit has fixed the issues we locally patched (and more), and for us to stop maintaining a fork of an old version of part of Gawk.

There's no known issue with the existing engine that I'm aware of which impacts git, but given ~7 years of bugfixes & improvements there's surely something.

Show 5 quoted lines
> Having these "fixup!" as separate patches on the list makes them
> smaller and easier to understand.  What do we want to do with them
> once they are applied?  Squash them all up, because these do not
> have their own explanations in their log message and it is not worth
> keeping them separate?

Please squash them all up into this commit ("compat/regex: update the gawk regex engine from upstream"), as noted having them as separate patches was a hack to get around mailing list limits.

Also, un-squashed they'd break the NO_REGEX=Y build for a few commits, which would be a pain during bisecting.

Show 34 quoted lines
>> The only reason this has a cover letter is to explain the !fixup
>> commits. IIRC the mailing list has a 100K limit, which this series
>> would violate, so I split up the second commit.
>>
>> Consider all these !fixup commits to have by Signed-off-by, easier to
>> say that here than to modify them all.
>>
>> Ævar Arnfjörð Bjarmason (7):
>>   compat/regex: add a README with a maintenance guide
>>   compat/regex: update the gawk regex engine from upstream
>>   fixup! compat/regex: update the gawk regex engine from upstream
>>   fixup! compat/regex: update the gawk regex engine from upstream
>>   fixup! compat/regex: update the gawk regex engine from upstream
>>   fixup! compat/regex: update the gawk regex engine from upstream
>>   fixup! compat/regex: update the gawk regex engine from upstream
>>
>>  Makefile                                           |   8 +-
>>  compat/regex/README                                |  21 +
>>  compat/regex/intprops.h                            | 448 +++++++++++++++++++++
>>  .../0001-Add-notice-at-top-of-copied-files.patch   | 120 ++++++
>>  .../0002-Remove-verify.h-use-from-intprops.h.patch |  41 ++
>>  compat/regex/regcomp.c                             | 356 +++++++++-------
>>  compat/regex/regex.c                               |  32 +-
>>  compat/regex/regex.h                               | 120 +++---
>>  compat/regex/regex_internal.c                      | 118 +++---
>>  compat/regex/regex_internal.h                      | 118 +++---
>>  compat/regex/regexec.c                             | 242 +++++------
>>  compat/regex/verify.h                              | 286 +++++++++++++
>>  12 files changed, 1487 insertions(+), 423 deletions(-)
>>  create mode 100644 compat/regex/README
>>  create mode 100644 compat/regex/intprops.h
>>  create mode 100644 compat/regex/patches/0001-Add-notice-at-top-of-copied-files.patch
>>  create mode 100644 compat/regex/patches/0002-Remove-verify.h-use-from-intprops.h.patch
>>  create mode 100644 compat/regex/verify.h
Previous: Junio C HamanoNext: Junio C Hamano
Message 19 of 21 in “Update the compat/regex engine from upstream”
  1. 0/7 Update the compat/regex engine from upstreamÆvar Arnfjörð Bjarmason, May 4, 2017
  2. 1/7 compat/regex: add a README with a maintenance guideÆvar Arnfjörð Bjarmason, May 4, 2017
  3. Junio C HamanoMay 12, 2017
  4. Johannes SchindelinMay 12, 2017
  5. Junio C HamanoMay 12, 2017
  6. arnold@skeeve.comMay 14, 2017
  7. Junio C HamanoMay 15, 2017
  8. Johannes SchindelinMay 15, 2017
  9. arnold@skeeve.comMay 15, 2017
  10. 2/7 compat/regex: update the gawk regex engine from upstreamÆvar Arnfjörð Bjarmason, May 4, 2017
  11. 3/7 fixup! compat/regex: update the gawk regex engine from upstreamÆvar Arnfjörð Bjarmason, May 4, 2017
  12. Johannes SixtMay 5, 2017
  13. 8/7 fixup! compat/regex: update the gawk regex engine from upstreamÆvar Arnfjörð Bjarmason, May 5, 2017
  14. 4/7 fixup! compat/regex: update the gawk regex engine from upstreamÆvar Arnfjörð Bjarmason, May 4, 2017
  15. 5/7 fixup! compat/regex: update the gawk regex engine from upstreamÆvar Arnfjörð Bjarmason, May 4, 2017
  16. 6/7 fixup! compat/regex: update the gawk regex engine from upstreamÆvar Arnfjörð Bjarmason, May 4, 2017
  17. 7/7 fixup! compat/regex: update the gawk regex engine from upstreamÆvar Arnfjörð Bjarmason, May 4, 2017
  18. Junio C HamanoMay 8, 2017
  19. Ævar Arnfjörð BjarmasonMay 8, 2017
  20. Junio C HamanoMay 8, 2017
  21. Junio C HamanoMay 12, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.