From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 01/27] onig: Use "foreign" automake strictness
Date: Fri, 18 Jul 2014 09:49:07 +0100 [thread overview]
Message-ID: <1405673347.26348.35.camel@ted> (raw)
In-Reply-To: <1405672966-25729-1-git-send-email-richard.purdie@linuxfoundation.org>
On Fri, 2014-07-18 at 09:42 +0100, Richard Purdie wrote:
> ---
> meta-oe/recipes-support/onig/files/configure.patch | 13 +++++++++++++
> meta-oe/recipes-support/onig/onig_5.9.3.bb | 3 ++-
> 2 files changed, 15 insertions(+), 1 deletion(-)
> create mode 100644 meta-oe/recipes-support/onig/files/configure.patch
Somehow the SoB lines got lost. I'll not spam the list again unless
someone wants me to, the commits are on:
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rpurdie/metaoe
complete with SoB lines.
Cheers,
Richard
prev parent reply other threads:[~2014-07-18 8:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 8:42 [PATCH 01/27] onig: Use "foreign" automake strictness Richard Purdie
2014-07-18 8:42 ` [PATCH 02/27] libol: " Richard Purdie
2014-07-18 8:42 ` [PATCH 03/27] usbpath: " Richard Purdie
2014-07-18 8:42 ` [PATCH 04/27] pidgin-otr: Add missing intltool-native DEPENDS Richard Purdie
2014-07-18 8:42 ` [PATCH 05/27] dejagnu: Use "foreign" automake strictness Richard Purdie
2014-07-18 8:42 ` [PATCH 06/27] hplip: Use "foreign" automake strictness and autotools-brokensep Richard Purdie
2014-07-18 8:42 ` [PATCH 07/27] claws-plugin-gtkhtml2: " Richard Purdie
2014-07-18 8:42 ` [PATCH 08/27] claws-plugin-rssyl: " Richard Purdie
2014-07-18 8:42 ` [PATCH 09/27] fbgrab: use autotools-brokensep (its not really autotools) Richard Purdie
2014-07-18 8:42 ` [PATCH 10/27] orrery: use autotools-brokensep Richard Purdie
2014-07-18 8:42 ` [PATCH 11/27] libsdl-image: Use "foreign" automake strictness Richard Purdie
2014-07-18 8:42 ` [PATCH 12/27] lcdproc: Remove floating dependency on libhid Richard Purdie
2014-07-18 8:42 ` [PATCH 13/27] libxfce4ui: Add missing gtk-doc inherit Richard Purdie
2014-07-18 8:42 ` [PATCH 14/27] ipsec-tools: Use "foreign" automake strictness Richard Purdie
2014-07-18 8:42 ` [PATCH 15/27] memcached: " Richard Purdie
2014-07-18 8:42 ` [PATCH 16/27] smbfsnet: " Richard Purdie
2014-07-18 8:42 ` [PATCH 17/27] engrave: Use autotools-brokensep to avoid build failures Richard Purdie
2014-07-18 8:42 ` [PATCH 18/27] efl: Use automake foreign for cpu/elmdentica/enjoy/ephoto/exalt-client/flame/forecasts/places/rain/uptime Richard Purdie
2014-07-18 8:42 ` [PATCH 19/27] subsurface: Fix libxml and libm build failures Richard Purdie
2014-07-18 8:42 ` [PATCH 20/27] " Richard Purdie
2014-07-18 8:42 ` [PATCH 21/27] rp-pppoe: Use "foreign" automake strictness Richard Purdie
2014-07-18 8:42 ` [PATCH 22/27] mtr: " Richard Purdie
2014-07-18 8:42 ` [PATCH 23/27] gegl: Use pkg-config for SDL Richard Purdie
2014-07-18 8:42 ` [PATCH 24/27] ode: Use "foreign" automake strictness Richard Purdie
2014-07-18 8:42 ` [PATCH 25/27] flite: Use autotools-brokensep Richard Purdie
2014-07-18 8:42 ` [PATCH 26/27] wvstreams: Add missing dbus/readline DEPENDS and use autotools-brokensep Richard Purdie
2014-07-18 8:42 ` [PATCH 27/27] libotr: Fix B!=S build failures Richard Purdie
2014-07-18 8:49 ` Richard Purdie [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=1405673347.26348.35.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-devel@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