GNU bug report logs - #22852
gzip-1.7 release coming 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>
Subject: bug#22845: closed (Re: bug#22852: gzip-1.7 release coming soon)
Date: Wed, 02 Mar 2016 17:02:02 +0000

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

Your bug report

#22852: FYI: release soon

which was filed against the gzip package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 22845 <at> debbugs.gnu.org.

-- 
22852: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22852
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: 22852-done <at> debbugs.gnu.org, Rusty Russell <rusty <at> rustcorp.com.au>
Subject: Re: bug#22852: gzip-1.7 release coming soon
Date: Wed, 2 Mar 2016 09:01:00 -0800

On Mon, Feb 29, 2016 at 8:49 AM, Jim Meyering <jim <at> meyering.net> wrote:
> [resending to the proper list -- first one went to bug-grep]
> Finally, here is a long-overdue upstream-ready --rsyncable
> patch for gzip. I've Cc'd Rusty Russel, who is listed as the author.
> I'll push this in the next day or so, so any improvements people
> can suggest in the mean time would be most welcome.
> Most of the changes came from some distro patches
> (not sure if it was debian or fedora, since I began this
> long ago). I added the test, the NEWS blurb, a few
> comments and the commit log.

Pushed as http://git.savannah.gnu.org/cgit/gzip.git/commit/?id=d6d48f427b4839352437be9688142f6733028d22

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

From: Jim Meyering <jim <at> meyering.net>
To: bug-grep <at> gnu.org
Subject: FYI: release soon
Date: Sun, 28 Feb 2016 21:31:57 -0800

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

I want to make a release soon.
The preceding release (gzip-1.6) was 2.5 years ago.

Here's a small admin change I've just pushed.
I suspect I'm the only one who noticed, because it
is triggered only via "make distcheck" when also
using automake built from automake.git's master branch.

[0001-maint-dist-check.mk-remove-.deps-dirs-before-compari.patch (text/x-patch, attachment)]

Previous Next

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