From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Fix config.mak.uname to allow cross-compilation
Date: Sun, 22 May 2016 22:45:43 +0200 [thread overview]
Message-ID: <20160522224543.7fc83f9e@free-electrons.com> (raw)
In-Reply-To: <2b22b774-92fe-c855-0c6e-af916a93dd30@mclink.it>
Hello,
On Sun, 22 May 2016 22:40:04 +0200, Mauro Condarelli wrote:
> > This patch cannot be applied, as it is a patch against Git directly,
> > while you should send patches against Buildroot. I.e, a patch that adds
> > a patch.
> I know.
> My patchset for BuildRoot is in "[Buildroot] [PATCH v2] Fix for GIT cross-compilation."
> and includes this patch.
> I sent this upstream and it's CC: here only FYI.
Ah, OK, I understand. You didn't break any rule, but I did not realize
this patch was for Git upstream and not for Buildroot :/
Thomsa
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-05-22 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-22 20:24 [Buildroot] [PATCH 1/1] Fix config.mak.uname to allow cross-compilation Mauro Condarelli
2016-05-22 20:24 ` Mauro Condarelli
2016-05-22 20:29 ` Thomas Petazzoni
2016-05-22 20:40 ` Mauro Condarelli
2016-05-22 20:45 ` 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=20160522224543.7fc83f9e@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