From: Phil Blundell <philb@gnu.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] eglibc: Restore ${PN} to before ${PN}-dev in PACKAGES
Date: Tue, 11 Sep 2012 19:11:30 +0100 [thread overview]
Message-ID: <1347387090.29443.36.camel@x121e.pbcl.net> (raw)
In-Reply-To: <CA+chaQdNwKQQg9d3hUK-XMQP-d21nBFxpic78yWmrJrWe=-o-w@mail.gmail.com>
Ah right, yeah, I guess so. Thanks, I'll re-send.
Do we have any roadmap for getting to a point where we don't need to
keep bumping PR by hand anymore?
p.
On Tue, 2012-09-11 at 20:09 +0200, Martin Jansa wrote:
> Missing PR bumps?
>
> On Tue, Sep 11, 2012 at 8:04 PM, Phil Blundell <philb@gnu.org> wrote:
> > Commit 13544fbc6217fee1731a6da1e2cf94901a500842 changed the ordering
> > of PACKAGES so that ${PN}-dev came before ${PN}. However, this caused
> > the FILES matching to go wrong if ${libdir} == ${base_libdir}. Fix this
> > by moving ${PN} ahead of ${PN}-dev once again.
prev parent reply other threads:[~2012-09-11 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 18:04 [PATCH] eglibc: Restore ${PN} to before ${PN}-dev in PACKAGES Phil Blundell
[not found] ` <CA+chaQdNwKQQg9d3hUK-XMQP-d21nBFxpic78yWmrJrWe=-o-w@mail.gmail.com>
2012-09-11 18:11 ` Phil Blundell [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=1347387090.29443.36.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--cc=martin.jansa@gmail.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