From: Phil Blundell <pb@pbcl.net>
To: rongqing.li@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] base-files: create /usr/lib/locale dir
Date: Tue, 18 Jun 2013 09:07:31 +0100 [thread overview]
Message-ID: <1371542851.5066.1.camel@pb-ThinkPad-R50e> (raw)
In-Reply-To: <b57b85f69322501fb617a01e625734cda1088b5e.1371539741.git.rongqing.li@windriver.com>
On Tue, 2013-06-18 at 15:19 +0800, rongqing.li@windriver.com wrote:
> - ${libdir} ${sbindir} ${datadir} \
> + ${libdir} /usr/lib/locale ${sbindir} ${datadir} \
This is bogus for a number of reasons. If the only reason for having it
is for lsbtest, can't it go in some LSB recipe?
p.
next prev parent reply other threads:[~2013-06-18 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 7:19 [PATCH 0/1] base-files: create /usr/lib/locale dir rongqing.li
2013-06-18 7:19 ` [PATCH 1/1] " rongqing.li
2013-06-18 8:07 ` Phil Blundell [this message]
2013-06-18 8:42 ` Rongqing Li
2013-06-18 9:12 ` Phil Blundell
2013-06-18 14:19 ` Mark Hatle
2013-06-18 8:24 ` [PATCH 0/1] " Burton, Ross
2013-06-18 8:39 ` Rongqing Li
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=1371542851.5066.1.camel@pb-ThinkPad-R50e \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=rongqing.li@windriver.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