GNU bug report logs - #16698
making the grep-2.17 release soon

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Jim Meyering <jim <at> meyering.net>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#16698: closed (making the grep-2.17 release soon)
Date: Sun, 09 Feb 2014 16:26:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Sun, 9 Feb 2014 08:25:08 -0800
with message-id <CA+8g5KGOs64QfFriMLB+11EL6L426ARpe7sJ=o4w=D0eTbCu6g <at> mail.gmail.com>
and subject line Re: bug#16698: making the grep-2.17 release soon
has caused the debbugs.gnu.org bug report #16698,
regarding making the grep-2.17 release soon
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
16698: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16698
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Jim Meyering <jim <at> meyering.net>
To: bug-grep <at> gnu.org
Subject: making the grep-2.17 release soon
Date: Sat, 8 Feb 2014 18:34:59 -0800

I want to make a release soon, preferably next week, with a first
snapshot tomorrow.
There is the pcre-related problem that can result in an infloop or
segfault, but that is in libpcre.  I may write a configure-time test
to detect that and, when found, turn off pcre support or just make
configure fail.  Maybe.

Does anyone have issues they'd like to see addressed for grep-2.17?

[Message part 3 (message/rfc822, inline)]

From: Jim Meyering <jim <at> meyering.net>
To: Aharon Robbins <arnold <at> skeeve.com>
Cc: 16698-done <at> debbugs.gnu.org
Subject: Re: bug#16698: making the grep-2.17 release soon
Date: Sun, 9 Feb 2014 08:25:08 -0800

On Sat, Feb 8, 2014 at 11:27 PM,  <arnold <at> skeeve.com> wrote:
> Jim Meyering <jim <at> meyering.net> wrote:
>
>> Does anyone have issues they'd like to see addressed for grep-2.17?
>
> Did we close the 'Lj' issue as "we're going to ignore this for now"?
> It sounds like yes, but I thought I'd double check.

Paul made a convincing case, so I'm treating the issue as closed-for-now.
It's trivial to reopen if/when we get some good rebuttal.

> If so, some of the code in dfa.c related to case folding could probably
> still use a little refactoring.  I can try to give that whirl if noone
> beats me to it.

Sounds good.  If you'd like to see that in 2.17, please post it ASAP.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.