From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 7/8] configs: add defconfig for Atmel sama5d3 Xplained
Date: Fri, 1 May 2015 09:33:35 +0200 [thread overview]
Message-ID: <20150501093335.7d7583d5@free-electrons.com> (raw)
In-Reply-To: <20150430151402.GG12076@piout.net>
Dear Alexandre Belloni,
On Thu, 30 Apr 2015 17:14:02 +0200, Alexandre Belloni wrote:
> > 'linux-3.18-at91' appears to be a branch which means that it could be
> > updated and break this config?
> >
> > I believe in order to ensure that a build is reproducible for everyone
> > that this should be a tag or commit SHA. This would also apply to all
> > your other new NAND configurations for the Atmel boards.
>
> That is the expected behaviour. This branch must not break. I'm not
> saying it won't break but if it ever breaks, it will definitively be
> fixed.
No, please don't use a branch. Never ever. This makes the build
non-reproducible. And also means that once a
linux-linux-3.18-at91.tar.gz tarball has been created in $(DL_DIR), it
is never redownloaded even if the branch is updated.
So please do like Ryan said: use a tag or a commit ID. Feel free to
update this commit ID or tag as often as you want by sending patches,
but don't use a branch name.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-05-01 7:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 12:51 [Buildroot] [PATCH 0/8] configs: defconfigs for Atmel boards Alexandre Belloni
2015-04-30 12:51 ` [Buildroot] [PATCH 1/8] configs: update at91sam9g45m10ek defconfig Alexandre Belloni
2015-04-30 12:51 ` [Buildroot] [PATCH 2/8] configs: add defconfig for Atmel at91sam9rlek Alexandre Belloni
2015-04-30 12:51 ` [Buildroot] [PATCH 3/8] configs: add defconfig for Atmel at91sam9x5ek Alexandre Belloni
2015-04-30 12:51 ` [Buildroot] [PATCH 4/8] configs: add defconfig for Atmel sama5d3xek Alexandre Belloni
2015-04-30 12:51 ` [Buildroot] [PATCH 5/8] configs: add defconfig for Atmel sama5d4ek Alexandre Belloni
2015-04-30 12:51 ` [Buildroot] [PATCH 6/8] configs: add defconfig for Atmel sama4d4 Xplained Ultra Alexandre Belloni
2015-05-01 7:35 ` Thomas Petazzoni
2015-04-30 12:51 ` [Buildroot] [PATCH 7/8] configs: add defconfig for Atmel sama5d3 Xplained Alexandre Belloni
2015-04-30 14:46 ` Ryan Barnett
2015-04-30 15:14 ` Alexandre Belloni
2015-04-30 15:16 ` Ryan Barnett
2015-05-01 7:33 ` Thomas Petazzoni [this message]
2015-04-30 12:51 ` [Buildroot] [PATCH 8/8] configs: rename atmel_xplained_defconfig Alexandre Belloni
2015-04-30 14:36 ` Ryan Barnett
2015-04-30 14:40 ` Alexandre Belloni
2015-04-30 14:33 ` [Buildroot] [PATCH 0/8] configs: defconfigs for Atmel boards Ryan Barnett
2015-04-30 14:40 ` Alexandre Belloni
2015-05-01 7:34 ` Thomas Petazzoni
2015-05-01 12:02 ` Arnout Vandecappelle
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=20150501093335.7d7583d5@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox