From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next 1/9] gstreamer1/gstreamer1: bump version to 1.10.1
Date: Tue, 22 Nov 2016 10:43:44 +0100 [thread overview]
Message-ID: <20161122104344.75f6bf44@free-electrons.com> (raw)
In-Reply-To: <20161122040710.xjuztgsjyckbbnax@tarshish>
Hello,
On Tue, 22 Nov 2016 06:07:10 +0200, Baruch Siach wrote:
> > Entire series applied to next, thanks!
>
> Patch 5/9 (gstreamer1/gst1-plugins-bad: bump version to 1.10.1) is not in next
> as of 8684b9b01e5f3.
Thanks for noticing, this was a mistake on my side. I now applied and
pushed this patch as well.
Thanks again,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-11-22 9:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 17:08 [Buildroot] [PATCH next 1/9] gstreamer1/gstreamer1: bump version to 1.10.1 Vicente Olivert Riera
2016-11-17 17:08 ` [Buildroot] [PATCH next 2/9] gstreamer1/gst1-plugins-base: " Vicente Olivert Riera
2016-11-17 17:08 ` [Buildroot] [PATCH next 3/9] gstreamer1/gst1-plugins-good: " Vicente Olivert Riera
2016-11-17 17:09 ` [Buildroot] [PATCH next 4/9] gstreamer1/gst1-plugins-ugly: " Vicente Olivert Riera
2016-11-17 17:09 ` [Buildroot] [PATCH next 5/9] gstreamer1/gst1-plugins-bad: " Vicente Olivert Riera
2016-11-17 17:09 ` [Buildroot] [PATCH next 6/9] gstreamer1/gst1-libav: " Vicente Olivert Riera
2016-11-17 17:09 ` [Buildroot] [PATCH next 7/9] gstreamer1/gst1-rtsp-server: " Vicente Olivert Riera
2016-11-17 17:09 ` [Buildroot] [PATCH next 8/9] gstreamer1/gst1-validate: " Vicente Olivert Riera
2016-11-17 17:09 ` [Buildroot] [PATCH next 9/9] gstreamer1/gst1-omx: " Vicente Olivert Riera
2016-11-21 22:17 ` [Buildroot] [PATCH next 1/9] gstreamer1/gstreamer1: " Thomas Petazzoni
2016-11-22 4:07 ` Baruch Siach
2016-11-22 4:12 ` Baruch Siach
2016-11-22 9:43 ` Thomas Petazzoni [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=20161122104344.75f6bf44@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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