From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] download/git: force gzip compression level 6
Date: Wed, 13 Sep 2017 07:07:14 +0200 [thread overview]
Message-ID: <20170913050714.GC3625@scaer> (raw)
In-Reply-To: <87shfr4n14.fsf@dell.be.48ers.dk>
Peter, All,
On 2017-09-12 23:36 +0200, Peter Korsgaard spake thusly:
> >>>>> "Petr" == Petr Kulhavy <brain@jikos.cz> writes:
>
> > Force gzip compression level 6 when calculating hash of a downloaded GIT repo.
> > To make sure the tar->gzip->checksum chain always provides consistent result.`
>
> > The script was relying on the default compression level, which must not be
> > necessarily consistent among different gzip versions. The level 6 is gzip's
> > current default compression level.
>
> Committed, thanks.
>
> Is this just a theoretical issue, or something you have really run into?
Theoretical, see this mail and the ensuing discussion:
http://lists.busybox.net/pipermail/buildroot/2017-September/202162.html
Yet, for consistency, it is good to force it.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-09-13 5:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 22:13 [Buildroot] [PATCH 1/1] download/git: force gzip compression level 6 Petr Kulhavy
2017-09-12 6:05 ` Yann E. MORIN
2017-09-12 21:36 ` Peter Korsgaard
2017-09-13 5:07 ` Yann E. MORIN [this message]
2017-09-21 13:41 ` Peter Korsgaard
2017-10-16 21:54 ` Peter Korsgaard
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=20170913050714.GC3625@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.