From: Junio C Hamano <gitster@pobox.com>
To: Carlo Arenas <carenas@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2019, #06; Fri, 23)
Date: Wed, 28 Aug 2019 08:10:34 -0700 [thread overview]
Message-ID: <xmqqo9091g2d.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAPUEspi0z7cjdH7J5=VKcG1jXbhi0EeJecs-ApT39PyhAWp2Qg@mail.gmail.com> (Carlo Arenas's message of "Wed, 28 Aug 2019 02:55:06 -0700")
Carlo Arenas <carenas@gmail.com> writes:
> On Fri, Aug 23, 2019 at 6:16 PM Junio C Hamano <gitster@pobox.com> wrote:
>>
>> * cb/pcre2-chartables-leakfix (2019-08-06) 3 commits
>> - grep: avoid leak of chartables in PCRE2
>> - grep: make PCRE2 aware of custom allocator
>> - grep: make PCRE1 aware of custom allocator
>>
>> WIP
>
> this was v3 and doesn't sufficiently address the issue raised on
> windows so might be better to drop it and requee it later ...
> we have two alternative versions of v6 that could be used as a reroll
> if you would rather do that, but will still not address the full set
> of issues that will be required to stabilize it into next.
It sounds like by queuing a premature iteration, by not picking up
updated ones and by not following the discussion very closely, I am
doing more harm than simply waiting, so let me step aside, drop this
one for now and let you folks figure it out.
Thanks.
prev parent reply other threads:[~2019-08-28 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-24 1:13 What's cooking in git.git (Aug 2019, #06; Fri, 23) Junio C Hamano
2019-08-28 9:55 ` Carlo Arenas
2019-08-28 15:10 ` Junio C Hamano [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqo9091g2d.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=carenas@gmail.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).