From: Alexander Marx <alexander.marx@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] gzip: Update to 1.8
Date: Tue, 17 May 2016 14:27:58 +0200 [thread overview]
Message-ID: <573B0E4E.3040203@ipfire.org> (raw)
In-Reply-To: <1463487864.24916.13.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]
Sorry, need to reboot after holidays .... running at 80%
Am 17.05.2016 um 14:24 schrieb Michael Tremer:
> Hi,
>
> just back from holiday and already fixing bugs. I like that.
>
> Unfortunately you forgot to include the bug number in the commit message. Please
> do that so the build system can automatically update and close the bug
> eventually.
>
> I will add it this time so you don't have to re-send this patch.
>
> Best,
> -Michael
>
> On Tue, 2016-05-17 at 14:10 +0200, Alexander Marx wrote:
>> This is an update-release
>>
>> gzip -l no longer falsely reports a write error when writing to a pipe.
>> [bug introduced in gzip-1.7]
>>
>> Port to Oracle Solaris Studio 12 on x86-64.
>> [bug present since at least gzip-1.2.4]
>>
>> When configuring gzip, ./configure DEFS='...-DNO_ASM...' now
>> suppresses assembler again. [bug introduced in gzip-1.3.5]
>>
>> Signed-off-by: Alexander Marx <alexander.marx(a)ipfire.org>
>> ---
>> gzip/gzip.nm | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/gzip/gzip.nm b/gzip/gzip.nm
>> index 1ba2326..a75fe44 100644
>> --- a/gzip/gzip.nm
>> +++ b/gzip/gzip.nm
>> @@ -4,7 +4,7 @@
>> #############################################################################
>> ##
>>
>> name = gzip
>> -version = 1.7
>> +version = 1.8
>> release = 1
>>
>> groups = Applications/Compression
next prev parent reply other threads:[~2016-05-17 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 12:10 Alexander Marx
2016-05-17 12:24 ` Michael Tremer
2016-05-17 12:27 ` Alexander Marx [this message]
2017-03-18 10:30 [PATCH] gzip: update " Marcel Lorenz
2017-04-06 9:05 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=573B0E4E.3040203@ipfire.org \
--to=alexander.marx@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox