From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [oe-commits] Richard Tollerton : font-util: Fix incorrect PKG_CONFIG_PATH
Date: Fri, 20 Feb 2015 12:50:03 +0000 [thread overview]
Message-ID: <1424436603.11836.42.camel@linuxfoundation.org> (raw)
In-Reply-To: <20150220124501.GB2322@jama>
On Fri, 2015-02-20 at 13:45 +0100, Martin Jansa wrote:
> On Tue, Feb 03, 2015 at 04:02:36PM +0000, Burton, Ross wrote:
> > On 3 February 2015 at 01:05, Richard Tollerton <rich.tollerton@ni.com>
> > wrote:
> >
> > > Done (and sent), and my apologies, because this exercise has made clear
> > > that I was wrong in several of the details here: None of the three
> > > patches were committed; I was confusing one of them with 89a29a3a, which
> > > was from a separate email. The confusion originated in 89a29a3a having
> > > been committed after I had already withdrawn it, which I forgot about
> > > over the holidays.
> > >
> >
> > That's probably my fault, sorry. Thanks for following up and resolving
> > this properly.
>
> Can you please merge those fixes before 1.8 is closed? Or at least
> revert the original patch which shouldn't be merged, until your comment
> for 1/3 is resolved.
>
> FWIW I haven't noticed v4 to resolve:
> https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg61018.html
We don't have the "right" patch for this yet. I don't want the fonts in
the sysroots, I agree we need to resolve the other issues though. I also
agree this needs fixing for 1.8, thanks for bringing it up.
Cheers,
Richard
next prev parent reply other threads:[~2015-02-20 12:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141219180841.C5F5A503BF@opal.openembedded.org>
2015-01-07 14:12 ` [oe-commits] Richard Tollerton : font-util: Fix incorrect PKG_CONFIG_PATH Martin Jansa
2015-01-08 12:01 ` Martin Jansa
2015-01-08 20:00 ` Richard Tollerton
2015-01-28 13:40 ` Martin Jansa
2015-01-29 9:21 ` Richard Tollerton
2015-02-02 18:57 ` Paul Eggleton
2015-02-03 1:05 ` Richard Tollerton
2015-02-03 16:02 ` Burton, Ross
2015-02-20 12:45 ` Martin Jansa
2015-02-20 12:50 ` Richard Purdie [this message]
2015-02-20 14:36 ` Martin Jansa
2015-02-20 15:27 ` Ben Shelton
2015-02-20 19:52 ` Ben Shelton
2015-02-20 20:13 ` Burton, Ross
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=1424436603.11836.42.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.