From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Revert "manual: Add notes about GitHub and hashes"
Date: Sun, 18 Oct 2015 18:02:19 +0200 [thread overview]
Message-ID: <20151018180219.037bcae1@free-electrons.com> (raw)
In-Reply-To: <CAGduivxzeH25hzV6Zd-pmm8wyMG-TgCkh88WTwCEaKZJw4NQ=Q@mail.gmail.com>
Dear Maxime Hadjinlian,
On Sun, 18 Oct 2015 17:32:23 +0200, Maxime Hadjinlian wrote:
> Should we wait FOSDEM where we said that if there was not any problem we
> would simply add all the missing hashes for GitHub packages ? Or we go back
> on what we said and we do it now ?
> And so, should we apply this now, or wait a bit ?
We are now requesting people adding new packages fetched from Github to
use the hash file, so our documentation should reflect that.
Adding "all" the missing hashes is not necessarily something we have to
do right now. We can wait to gain a bit of knowledge/experience using
the hashes on newly added packages (or existing packages when they are
bumped), and if it continues to work fine, we'll add all hashes at some
point in the future.
I.e, please don't send a 200 patches patch series adding hashes for all
github downloaded packages.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-10-18 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 15:26 [Buildroot] [PATCH] Revert "manual: Add notes about GitHub and hashes" Samuel Martin
2015-10-18 15:32 ` Maxime Hadjinlian
2015-10-18 16:02 ` Thomas Petazzoni [this message]
2015-10-18 16:00 ` Thomas Petazzoni
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=20151018180219.037bcae1@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 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.