[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#22845: closed (FYI: release soon)

From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#22845: closed (FYI: release soon)
Date: Wed, 02 Mar 2016 17:02:02 +0000

Your message dated Wed, 2 Mar 2016 09:01:00 -0800
with message-id <address@hidden>
and subject line Re: bug#22852: gzip-1.7 release coming soon
has caused the debbugs.gnu.org bug report #22852,
regarding FYI: release soon
to be marked as done.

(If you believe you have received this mail in error, please contact

22852: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22852
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: FYI: release soon Date: Sun, 28 Feb 2016 21:31:57 -0800
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.

Attachment: 0001-maint-dist-check.mk-remove-.deps-dirs-before-compari.patch
Description: Text Data

--- End Message ---
--- Begin Message --- 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 <address@hidden> 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 

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]