All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] libowl updates
Date: Fri, 17 Aug 2012 13:57:42 -0700	[thread overview]
Message-ID: <502EB046.3080704@linux.intel.com> (raw)
In-Reply-To: <cover.1344884443.git.ross.burton@intel.com>

On 08/13/2012 12:01 PM, Ross Burton wrote:
> Patches were merged upstream, so drop them and bump srcrev.
>
> The following changes since commit 2dec760b79bb7e2e79c33c5127fa64685bd86a18:
>
>    foomatic: fix perl path for target (2012-08-08 10:06:00 +0100)
>
> are available in the git repository at:
>
>    git://git.yoctoproject.org/poky-contrib ross/owl
>
> for you to fetch changes up to d3e664ba768f4485f8d7984a86c571cf43815497:
>
>    libowl-av: patches merged upstream, bump srcrev (2012-08-10 15:47:00 +0300)
>
> ----------------------------------------------------------------
> Ross Burton (2):
>        owl-video: patches pushed upstream, so bump srcrev
>        libowl-av: patches merged upstream, bump srcrev
>
>   .../libowl-av/gst_change_state.patch               |   42 --------------------
>   .../owl-video-widget/libowl-av/make-382.patch      |   13 ------
>   .../recipes-sato/owl-video-widget/libowl-av_git.bb |    8 ++--
>   .../owl-video/gtk_multithread_safe.patch           |   40 -------------------
>   .../owl-video-widget/owl-video/make-382.patch      |   17 --------
>   .../recipes-sato/owl-video-widget/owl-video_git.bb |    8 ++--
>   6 files changed, 6 insertions(+), 122 deletions(-)
>   delete mode 100644 meta/recipes-sato/owl-video-widget/libowl-av/gst_change_state.patch
>   delete mode 100644 meta/recipes-sato/owl-video-widget/libowl-av/make-382.patch
>   delete mode 100644 meta/recipes-sato/owl-video-widget/owl-video/gtk_multithread_safe.patch
>   delete mode 100644 meta/recipes-sato/owl-video-widget/owl-video/make-382.patch
>
Merged into OE-Core

Thanks
	Sau!


> Ross Burton (2):
>    owl-video: patches pushed upstream, so bump srcrev
>    libowl-av: patches merged upstream, bump srcrev
>
>   .../libowl-av/gst_change_state.patch               |   42 --------------------
>   .../owl-video-widget/libowl-av/make-382.patch      |   13 ------
>   .../recipes-sato/owl-video-widget/libowl-av_git.bb |    8 ++--
>   .../owl-video/gtk_multithread_safe.patch           |   40 -------------------
>   .../owl-video-widget/owl-video/make-382.patch      |   17 --------
>   .../recipes-sato/owl-video-widget/owl-video_git.bb |    8 ++--
>   6 files changed, 6 insertions(+), 122 deletions(-)
>   delete mode 100644 meta/recipes-sato/owl-video-widget/libowl-av/gst_change_state.patch
>   delete mode 100644 meta/recipes-sato/owl-video-widget/libowl-av/make-382.patch
>   delete mode 100644 meta/recipes-sato/owl-video-widget/owl-video/gtk_multithread_safe.patch
>   delete mode 100644 meta/recipes-sato/owl-video-widget/owl-video/make-382.patch
>



      parent reply	other threads:[~2012-08-17 21:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 19:01 [PATCH 0/2] libowl updates Ross Burton
2012-08-13 19:01 ` [PATCH 1/2] owl-video: patches pushed upstream, so bump srcrev Ross Burton
2012-08-13 19:01 ` [PATCH 2/2] libowl-av: patches merged upstream, " Ross Burton
2012-08-17 20:57 ` Saul Wold [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=502EB046.3080704@linux.intel.com \
    --to=sgw@linux.intel.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 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.