From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCHv3] dbus: clean up dbus-x11 packaging
Date: Fri, 27 May 2011 00:30:12 +0100 [thread overview]
Message-ID: <1306452612.27470.217.camel@rex> (raw)
In-Reply-To: <1306439148-9595-1-git-send-email-koen@dominion.thruhere.net>
On Thu, 2011-05-26 at 21:45 +0200, Koen Kooi wrote:
> Martin Jansa spotted some differences with OE dev, which this commit fixes:
>
> * dbus-launch is mentioned twice in FILES
> * dbus-x11 should drag in dbus-1
>
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
>
> Try 3, now with git --amend working properly. With a special thanks to Martin who tells me about these stupid typos on IRC
>
> meta/recipes-core/dbus/dbus.inc | 2 +-
> meta/recipes-core/dbus/dbus_1.4.1.bb | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Merged to master, thanks (although I screwed up merging the right patch
too).
Cheers,
Richard
prev parent reply other threads:[~2011-05-26 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 19:45 [PATCHv3] dbus: clean up dbus-x11 packaging Koen Kooi
2011-05-26 23:30 ` 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=1306452612.27470.217.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--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