From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] cmake : bump to version 3.0.2
Date: Mon, 22 Sep 2014 19:08:03 +0200 [thread overview]
Message-ID: <20140922190803.5af135e6@free-electrons.com> (raw)
In-Reply-To: <1411385468-24878-1-git-send-email-jeremy.rosen@openwide.fr>
Dear J?r?my Rosen,
On Mon, 22 Sep 2014 13:31:07 +0200, J?r?my Rosen wrote:
> Signed-off-by: J?r?my Rosen <jeremy.rosen@openwide.fr>
> ---
> ...not-prepend-CMake-root-path-when-searchin.patch | 38 ----------------------
> package/cmake/cmake.mk | 4 +--
> 2 files changed, 2 insertions(+), 40 deletions(-)
> delete mode 100644 package/cmake/cmake-0001-FindQt4-do-not-prepend-CMake-root-path-when-searchin.patch
Patch applied, thanks. However, there was one missing information: the
explanation of why the
cmake-0001-FindQt4-do-not-prepend-CMake-root-path-when-searchin.patch
gets removed. So I had to go check the upstream CMake Git repository to
verify that indeed a similar change had been merged. I've edited the
commit log to mention this.
See
http://git.buildroot.net/buildroot/commit/?id=4aef37b683a637c8755a8b197a46aa30674c2074.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-22 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 11:31 [Buildroot] [PATCH v2] cmake : bump to version 3.0.2 Jérémy Rosen
2014-09-22 11:31 ` [Buildroot] [PATCH v2] swig: add symlink to /usr/bin/swig2.0 Jérémy Rosen
2014-09-22 12:23 ` Thomas Petazzoni
2014-09-22 14:12 ` Samuel Martin
2014-09-22 17:29 ` Thomas Petazzoni
2014-09-22 17:08 ` Thomas Petazzoni [this message]
2014-09-23 6:51 ` [Buildroot] [PATCH v2] cmake : bump to version 3.0.2 Jeremy Rosen
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=20140922190803.5af135e6@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