From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] procrank_linux: new package
Date: Tue, 23 Feb 2016 22:06:11 +0100 [thread overview]
Message-ID: <20160223220611.3a898b61@free-electrons.com> (raw)
In-Reply-To: <56CCC2BE.6060901@free-electrons.com>
Gustavo,
On Tue, 23 Feb 2016 17:36:14 -0300, Gustavo Zacarias wrote:
> On 23/02/16 17:26, Arnout Vandecappelle wrote:
>
> > You forgot to add a hash file.
>
> Are github pull hashes stable? (i.e. not tagged)
Yes, at least from our experience of the last months adding hashes for
Github-sourced packages.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-23 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 15:54 [Buildroot] [PATCH] procrank_linux: new package gustavo.zacarias at free-electrons.com
2016-02-23 20:26 ` Arnout Vandecappelle
2016-02-23 20:36 ` Gustavo Zacarias
2016-02-23 21:06 ` Thomas Petazzoni [this message]
2016-02-23 21:35 ` Arnout Vandecappelle
2016-03-06 15:13 ` Thomas Petazzoni
2016-03-06 15:13 ` 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=20160223220611.3a898b61@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