From: alexander.kanavin@linux.intel.com
To: "Khem Raj" <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/4] clutter: Upgrade 1.24.2 -> 1.25.6
Date: Mon, 22 Feb 2016 13:35:59 +0200 (EET) [thread overview]
Message-ID: <60357.10.252.15.38.1456140959.squirrel@linux.intel.com> (raw)
In-Reply-To: <1456123857-8502-2-git-send-email-raj.khem@gmail.com>
> Here is changes between two versions
> https://git.gnome.org/browse/clutter/log/?qt=range&q=1.24.2..1.25.6
>
> For me it has configure fixes to compile it with clang
Gnome projects have an odd-even version scheme, and 1.25 is a development
release. So you need to backport the necessary fixes, or wait until 1.26.
Alex
next prev parent reply other threads:[~2016-02-22 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 6:50 [PATCH 1/4] Upgrade systemd to 229 Khem Raj
2016-02-22 6:50 ` [PATCH 2/4] clutter: Upgrade 1.24.2 -> 1.25.6 Khem Raj
2016-02-22 11:35 ` alexander.kanavin [this message]
2016-02-22 6:50 ` [PATCH 3/4] security_flags: Disable ssp when compiling uclibc Khem Raj
2016-02-22 6:50 ` [PATCH 4/4] uclibc: Do not use immediate expansion operator Khem Raj
2016-02-22 12:52 ` [PATCH 1/4] Upgrade systemd to 229 Alexander Kanavin
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=60357.10.252.15.38.1456140959.squirrel@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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