GNU bug report logs - #24429
New mailing list: grep-devel@gnu.org, and preparing for a new release

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#24429: closed (New mailing list: grep-devel <at> gnu.org, and
 preparing for a new release)
Date: Fri, 16 Sep 2016 03:15:02 +0000

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

Your message dated Thu, 15 Sep 2016 20:14:12 -0700
with message-id <CA+8g5KHgdRpULEnLyTSW9rEDp+UqXRsUGZBZgArdawGDAHdC3Q <at> mail.gmail.com>
and subject line Re: bug#24429: New mailing list: grep-devel <at> gnu.org, and preparing for a new release
has caused the debbugs.gnu.org bug report #24429,
regarding New mailing list: grep-devel <at> gnu.org, and preparing for a new release
to be marked as done.

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


-- 
24429: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24429
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: grep-devel <at> gnu.org, bug-grep <at> gnu.org
Subject: New mailing list: grep-devel <at> gnu.org, and preparing for a new release
Date: Tue, 13 Sep 2016 12:05:35 -0700

If you're interested in grep development and announcements, please
subscribe to the new list, grep-devel <at> gnu.org, via this link:
https://lists.gnu.org/mailman/listinfo/grep-devel.

Why? The bug-grep list is for bug reports: every new thread there gets
its own auto-created "issue" that must then be triaged and eventually
closed. It does not make sense to require that for many announcement
or discussion-style (non-bug) threads.

I will probably post about the next release to the bug list, but not after that.

In case I have your attention, still, please chime in if you have any
non-invasive/safe pending patches, because I want to make a new
release soon, in large part for this bug fix:

** Bug fixes

  Grep no longer omits output merely because it follows an output line
  suppressed due to encoding errors.  [bug introduced in grep-2.21]

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

From: Jim Meyering <jim <at> meyering.net>
To: grep-devel <at> gnu.org, 24429-done <at> debbugs.gnu.org
Subject: Re: bug#24429: New mailing list: grep-devel <at> gnu.org, and preparing
 for a new release
Date: Thu, 15 Sep 2016 20:14:12 -0700

On Tue, Sep 13, 2016 at 12:05 PM, Jim Meyering <jim <at> meyering.net> wrote:
> If you're interested in grep development and announcements, please
> subscribe to the new list, grep-devel <at> gnu.org, via this link:
> https://lists.gnu.org/mailman/listinfo/grep-devel.
>
> Why? The bug-grep list is for bug reports: every new thread there gets
> its own auto-created "issue" that must then be triaged and eventually
> closed. It does not make sense to require that for many announcement
> or discussion-style (non-bug) threads.
>
> I will probably post about the next release to the bug list, but not after that.
>
> In case I have your attention, still, please chime in if you have any
> non-invasive/safe pending patches, because I want to make a new
> release soon, in large part for this bug fix:
>
> ** Bug fixes
>
>   Grep no longer omits output merely because it follows an output line
>   suppressed due to encoding errors.  [bug introduced in grep-2.21]

No one replied, so I am preparing a pre-release snapshot.

Previous Next

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