From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] fs/common.mk: do not store original names and timestamps when creating GZIP rootfs
Date: Wed, 17 Jul 2019 08:47:15 +0200 [thread overview]
Message-ID: <20190717084715.5614d171@windsurf> (raw)
In-Reply-To: <20190716174214.11914-1-itsatharva@gmail.com>
Hello Atharva,
On Tue, 16 Jul 2019 23:12:13 +0530
Atharva Lele <itsatharva@gmail.com> wrote:
> We don't use the GZIP environment variable to store GZIP options
> anymore. So explicitly add -n argument to the GZIP call to ensure
> reproducibility.
>
> Signed-off-by: Atharva Lele <itsatharva@gmail.com>
> Acked-by: Yann E. MORIN <yann.morin.1998@free.fr>
> ---
> Changes v1 -> v2:
> - Reversed order of patches
> ---
> fs/common.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Both applied, thanks! I had to reword a little bit the commit log of
PATCH 1/2, because the wording was no longer really appropriate after
you swapped the order of the two patches.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-07-17 6:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 17:42 [Buildroot] [PATCH v2 1/2] fs/common.mk: do not store original names and timestamps when creating GZIP rootfs Atharva Lele
2019-07-16 17:42 ` [Buildroot] [PATCH v2 2/2] Makefile: don't export GZIP environment variable Atharva Lele
2019-08-04 20:12 ` Peter Korsgaard
2019-07-17 6:47 ` Thomas Petazzoni [this message]
2019-08-04 20:12 ` [Buildroot] [PATCH v2 1/2] fs/common.mk: do not store original names and timestamps when creating GZIP rootfs 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=20190717084715.5614d171@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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.