GNU bug report logs - #18642
preparing for a new release

Previous Next

Package: grep;

Reported by: Jim Meyering <jim <at> meyering.net>

Date: Mon, 6 Oct 2014 04:15:02 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log

Message #16 received at 18642-done <at> debbugs.gnu.org (full text, mbox):

From: Norihiro Tanaka <noritnk <at> kcn.ne.jp>
To: Jim Meyering <jim <at> meyering.net>
Cc: 18642-done <at> debbugs.gnu.org
Subject: Re: bug#18642: preparing for a new release
Date: Tue, 07 Oct 2014 23:37:33 +0900

Jim Meyering <jim <at> meyering.net> wrote:
> As you know, for any bug fix, we try hard to provide the following:
> 
>   - test case
>   - NEWS entry describing the problem and identifying affected releases
>   - a commit log attributing the precise commit that introduced the bug
> 
> Can you provide at least a test case?
> 
> BTW, I still have not attributed the commit between 2.19 and 2.20
> for the most recently described (in NEWS) bug fix.

Sorry, I investigated many cases, but I couldn't find it.

When this bug is reproduced, must be s == 0 and s1 > 0 and
d->newlines[s] != d->newlines[s1].  In addition, they mustn't be
updated until reaches a next newline.

I believe that all of them is never filled at the same time.  So I think
once I close the bug without fix.
This bug report was last modified 10 years and 275 days ago.

Previous Next

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