From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] Fix gupnp-tools missing dependency
Date: Fri, 27 May 2011 23:21:20 +0100 [thread overview]
Message-ID: <1306534880.27470.306.camel@rex> (raw)
In-Reply-To: <cover.1306520840.git.sgw@linux.intel.com>
On Fri, 2011-05-27 at 11:28 -0700, Saul Wold wrote:
> Fix missing dependency for M1 Builds
>
>
> The following changes since commit 4786ecdf7cd427089464dcb62579110d494e7cd7:
>
> License Field Cleanup: Non-standard field names (2011-05-27 18:27:04 +0100)
>
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib sgw/fix
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/fix
>
> Saul Wold (1):
> gupnp-tools: Add gupnp-av to DEPENDS
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-05-27 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 18:28 [PATCH 0/1] Fix gupnp-tools missing dependency Saul Wold
2011-05-27 18:28 ` [PATCH 1/1] gupnp-tools: Add gupnp-av to DEPENDS Saul Wold
2011-05-27 22:21 ` 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=1306534880.27470.306.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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