From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0 of 2 v3] Use full revision ID for git packages
Date: Sat, 2 Nov 2013 16:24:47 +0100 [thread overview]
Message-ID: <20131102162447.7acb9307@skate> (raw)
In-Reply-To: <patchbomb.1383404246@argentina>
Dear Thomas De Schampheleire,
On Sat, 02 Nov 2013 15:57:26 +0100, Thomas De Schampheleire wrote:
>
> As discussed recently, we should use full git commit IDs instead of
> abbreviated ones.
>
> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Both patches applied to for-peter-2013.11, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2013-11-02 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 14:57 [Buildroot] [PATCH 0 of 2 v3] Use full revision ID for git packages Thomas De Schampheleire
2013-11-02 14:57 ` [Buildroot] [PATCH 1 of 2 v3] manual: github commits should be specified in full Thomas De Schampheleire
2013-11-02 15:01 ` Samuel Martin
2013-11-02 14:57 ` [Buildroot] [PATCH 2 of 2 v3] git packages: use full revision hash Thomas De Schampheleire
2013-11-02 15:06 ` Yann E. MORIN
2013-11-02 15:24 ` 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=20131102162447.7acb9307@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