From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/7] Update for 2015.11.1
Date: Mon, 1 Feb 2016 08:22:23 +0100 [thread overview]
Message-ID: <20160201082223.51457765@free-electrons.com> (raw)
In-Reply-To: <1454289936-10654-2-git-send-email-mc5686@mclink.it>
Dear Mauro Condarelli,
On Mon, 1 Feb 2016 02:25:30 +0100, Mauro Condarelli wrote:
> From: Peter Korsgaard <peter@korsgaard.com>
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> Signed-off-by: Mauro Condarelli <mc5686@mclink.it>
This patch shouldn't be part of your patch series, it is already part
of the Git history.
Also, when sending patches, you shouldn't base your branch on
2015.11.1, but rather on the current master branch.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-01 7:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 1:25 [Buildroot] [PATCH 0/7] crossbar package and its dependencies Mauro Condarelli
2016-02-01 1:25 ` [Buildroot] [PATCH 1/7] Update for 2015.11.1 Mauro Condarelli
2016-02-01 7:22 ` Thomas Petazzoni [this message]
2016-02-01 1:25 ` [Buildroot] [PATCH 2/7] Additions necessary to compile Crossbar.io Mauro Condarelli
2016-02-01 7:22 ` Thomas Petazzoni
2016-02-01 1:25 ` [Buildroot] [PATCH 3/7] croosbar moved to buildroot Mauro Condarelli
2016-02-01 7:24 ` Thomas Petazzoni
[not found] ` <56AF1D2B.30202@mclink.it>
2016-02-01 11:19 ` Thomas Petazzoni
2016-02-01 1:25 ` [Buildroot] [PATCH 4/7] croosbar moved to buildroot (2) Mauro Condarelli
2016-02-01 7:25 ` Thomas Petazzoni
2016-02-01 1:25 ` [Buildroot] [PATCH 5/7] update of .hash files Mauro Condarelli
2016-02-01 7:26 ` Thomas Petazzoni
2016-02-01 1:25 ` [Buildroot] [PATCH 6/7] Dependencies added to package python-crossbar Mauro Condarelli
2016-02-01 1:25 ` [Buildroot] [PATCH 7/7] Further dependencies installed Mauro Condarelli
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=20160201082223.51457765@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