From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] git sourced packages
Date: Fri, 23 Nov 2012 00:14:17 +0100 [thread overview]
Message-ID: <20121123001417.6020c812@skate> (raw)
In-Reply-To: <140A1F4F62E34D098AF770FE7C37486A@JohanW7>
Dear Sagaert Johan,
On Thu, 22 Nov 2012 22:08:11 +0100, Sagaert Johan wrote:
> I think it would be a good idea to always specify a hash or tag when packages are sourced from git.
> There i no way otherwise to be sure what you are actually building.
I think this is what we already do. Which package(s) do you think are
not matching this?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-11-22 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 21:08 [Buildroot] git sourced packages Sagaert Johan
2012-11-22 23:14 ` Thomas Petazzoni [this message]
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=20121123001417.6020c812@skate \
--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