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

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 18642 in the body.
You can then email your comments to 18642 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: bug-grep <at> gnu.org
Subject: preparing for a new release
Date: Sun, 5 Oct 2014 21:13:42 -0700

Norihiro's latest fix is for a bug that is significant enough
that I would feel remiss not to make a release soon.

Here is one patch that looks worth including:
  #17715 dfa: build struct dfamust on demand

Any other suggestions for changes to be included?

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

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

Jim Meyering <jim <at> meyering.net> wrote:
> Norihiro's latest fix is for a bug that is significant enough
> that I would feel remiss not to make a release soon.
> 
> Here is one patch that looks worth including:
>   #17715 dfa: build struct dfamust on demand
> 
> Any other suggestions for changes to be included?
> 

Thanks.  I sent a patch to fix a potential bug.  Could you review it?

http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18645

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

From: Jim Meyering <jim <at> meyering.net>
To: Norihiro Tanaka <noritnk <at> kcn.ne.jp>
Cc: 18642 <at> debbugs.gnu.org
Subject: Re: bug#18642: preparing for a new release
Date: Mon, 6 Oct 2014 12:30:28 -0700

On Mon, Oct 6, 2014 at 8:48 AM, Norihiro Tanaka <noritnk <at> kcn.ne.jp> wrote:
> Jim Meyering <jim <at> meyering.net> wrote:
>> Norihiro's latest fix is for a bug that is significant enough
>> that I would feel remiss not to make a release soon.
>>
>> Here is one patch that looks worth including:
>>   #17715 dfa: build struct dfamust on demand
>>
>> Any other suggestions for changes to be included?
>>
>
> Thanks.  I sent a patch to fix a potential bug.  Could you review it?
>
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18645

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.

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.

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

From: Norihiro Tanaka <noritnk <at> kcn.ne.jp>
To: 18642 <at> debbugs.gnu.org
Cc: Jim Meyering <jim <at> meyering.net>
Subject: Re: bug#18642: preparing for a new release
Date: Thu, 09 Oct 2014 07:41:56 +0900

Norihiro Tanaka <noritnk <at> kcn.ne.jp> wrote:
> 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.

Sorry, I have closed bug#18642 instead of bug#18645 by my mistake.  This
bug isn't done.  Can you re-open it?

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

From: Jim Meyering <jim <at> meyering.net>
To: Norihiro Tanaka <noritnk <at> kcn.ne.jp>
Cc: 18642 <18642 <at> debbugs.gnu.org>
Subject: Re: bug#18642: preparing for a new release
Date: Wed, 8 Oct 2014 20:37:00 -0700

On Wed, Oct 8, 2014 at 3:41 PM, Norihiro Tanaka <noritnk <at> kcn.ne.jp> wrote:
> Norihiro Tanaka <noritnk <at> kcn.ne.jp> wrote:
>> 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.
>
> Sorry, I have closed bug#18642 instead of bug#18645 by my mistake.  This
> bug isn't done.  Can you re-open it?

18642 was auto-filed for my message saying I want to make a release soon.
That is not an issue that deserves to have an open bug number, so it
is fine that you closed it.

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

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Jim Meyering <jim <at> meyering.net>, Norihiro Tanaka <noritnk <at> kcn.ne.jp>
Cc: 18642 <18642-done <at> debbugs.gnu.org>
Subject: Re: bug#18642: preparing for a new release
Date: Wed, 08 Oct 2014 21:30:48 -0700

Jim Meyering wrote:
> it
> is fine that you closed it.

Hah!  And I reopened it at his request.  Closing it again.

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

From: Norihiro Tanaka <noritnk <at> kcn.ne.jp>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: Jim Meyering <jim <at> meyering.net>, 18642 <18642-done <at> debbugs.gnu.org>
Subject: Re: bug#18642: preparing for a new release
Date: Thu, 09 Oct 2014 22:41:31 +0900

Paul Eggert <eggert <at> cs.ucla.edu> wrote:
> Jim Meyering wrote:
> > it
> > is fine that you closed it.
> 
> Hah!  And I reopened it at his request.  Closing it again.

Thanks.  I'a sorry to confuse you.

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

From: Norihiro Tanaka <noritnk <at> kcn.ne.jp>
To: Jim Meyering <jim <at> meyering.net>
Cc: 18642 <at> debbugs.gnu.org
Subject: Re: bug#18642: preparing for a new release
Date: Thu, 23 Oct 2014 08:44:48 +0900

Jim Meyering <jim <at> meyering.net> wrote:
> Norihiro's latest fix is for a bug that is significant enough
> that I would feel remiss not to make a release soon.
> 
> Here is one patch that looks worth including:
>   #17715 dfa: build struct dfamust on demand
> 
> Any other suggestions for changes to be included?

Although I submitted some patches after received this message, reak bugs
are bug#18631 and bug#18685, and bug#18631 doesn't affair for users.  So,
I think that only bug#18685 should be fixed until a next release.

Previous Next

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