From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1 of 2 v2] manual: github commits should be specified in full
Date: Sat, 2 Nov 2013 14:44:46 +0100 [thread overview]
Message-ID: <20131102144446.6c1e05b8@skate> (raw)
In-Reply-To: <f6fb6654af62045239ca.1383398537@argentina>
Dear Thomas De Schampheleire,
On Sat, 02 Nov 2013 14:22:17 +0100, Thomas De Schampheleire wrote:
> @@ -53,5 +53,4 @@ FOO_SITE = http://github.com/<user>/<pac
> - The tarball name generated by github matches the default one from
> Buildroot (e.g.: +foo-1234567.tar.gz+),
Samuel also suggested that this example should use a full git commit
ID, no?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-02 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 13:22 [Buildroot] [PATCH 0 of 2 v2] Use full revision ID for git packages Thomas De Schampheleire
2013-11-02 13:22 ` [Buildroot] [PATCH 1 of 2 v2] manual: github commits should be specified in full Thomas De Schampheleire
2013-11-02 13:44 ` Thomas Petazzoni [this message]
2013-11-02 14:51 ` Thomas De Schampheleire
2013-11-02 13:22 ` [Buildroot] [PATCH 2 of 2 v2] git packages: use full revision hash Thomas De Schampheleire
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=20131102144446.6c1e05b8@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