From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] blackbox: rename patches to add sequence numbers
Date: Wed, 18 Dec 2013 10:49:30 +0100 [thread overview]
Message-ID: <20131218104930.0983eeac@skate> (raw)
In-Reply-To: <1387296884-27777-1-git-send-email-Vincent.Riera@imgtec.com>
Dear Vicente Olivert Riera,
On Tue, 17 Dec 2013 16:14:43 +0000, Vicente Olivert Riera wrote:
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> ...0.70.1-gcc43.patch => blackbox-002-gcc43.patch} | 0
> ... blackbox-003-gcc46-textpropertytostring.patch} | 0
> 2 files changed, 0 insertions(+), 0 deletions(-)
> rename package/blackbox/{blackbox-0.70.1-gcc43.patch => blackbox-002-gcc43.patch} (100%)
> rename package/blackbox/{blackbox-0.70.1-gcc46-textpropertytostring.patch => blackbox-003-gcc46-textpropertytostring.patch} (100%)
It is a little bit weird that the first patch was not renamed in this
commit, but instead renamed in PATCH 2/2, mixed with some other changes
in the patch itself.
Both patches have now be applied by Peter, so it's too late, but it
would have been good to get this right.
Thanks for those contributions anyway!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-12-18 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 16:14 [Buildroot] [PATCH 1/2] blackbox: rename patches to add sequence numbers Vicente Olivert Riera
2013-12-17 16:14 ` [Buildroot] [PATCH 2/2] blackbox: merge patch and fix linkage problem Vicente Olivert Riera
2013-12-17 19:39 ` [Buildroot] [PATCH 1/2] blackbox: rename patches to add sequence numbers Peter Korsgaard
2013-12-18 9:49 ` Thomas Petazzoni [this message]
2013-12-18 10:25 ` Peter Korsgaard
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=20131218104930.0983eeac@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 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.