From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/4] gcr: remove Vala dependency
Date: Fri, 06 Nov 2015 16:37:43 +0200 [thread overview]
Message-ID: <563CBB37.8090103@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LbgKKZC+iGewifxjOO5agRPq=j_fFw0von0Ap+80a+Nhw@mail.gmail.com>
On 11/04/2015 10:20 PM, Burton, Ross wrote:
> Retracting this, gcr needs vala's m4 file. Back to wondering if we
> should have a vala-stub too...
Upcoming introspection patchset also adds a bonus vapigen support, so
you don't really need to do these disable-vala fixes.
Alex
next prev parent reply other threads:[~2015-11-06 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 19:46 [PATCH 1/4] readline: rename patch to contain CVE reference Ross Burton
2015-11-04 19:46 ` [PATCH 2/4] unzip: rename patch to reflect CVE fix Ross Burton
2015-11-04 19:47 ` [PATCH 3/4] gcr: remove Vala dependency Ross Burton
2015-11-04 20:20 ` Burton, Ross
2015-11-06 14:37 ` Alexander Kanavin [this message]
2015-11-04 19:47 ` [PATCH 4/4] at: modify sources in do_patch Ross Burton
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=563CBB37.8090103@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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