From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: kai.kang@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 0/8] gstreamer1.0: 1.12.4 -> 1.14.0
Date: Mon, 30 Apr 2018 15:58:37 +0300 [thread overview]
Message-ID: <d33b20e6-d156-6610-1e12-aac3b0932959@linux.intel.com> (raw)
In-Reply-To: <cover.1524640773.git.kai.kang@windriver.com>
On 04/25/2018 10:23 AM, kai.kang@windriver.com wrote:
> gstreamer1.0: 1.12.4 -> 1.14.0
> gstreamer1.0-plugins-base: 1.12.4 -> 1.14.0
> gstreamer1.0-plugins-bad: 1.12.4 -> 1.14.0
> gstreamer1.0-plugins-ugly: 1.12.4 -> 1.14.0
> gstreamer1.0-plugins-good: 1.12.4 -> 1.14.0
> gstreamer1.0-libav: 1.12.4 -> 1.14.0
> gst-validate: 1.12.4 -> 1.14.0
> gstreamer1.0: upgrade other packages to 1.14.0
Are you aware if they plan to drop autotools and provide only meson
builds, and when?
Alex
prev parent reply other threads:[~2018-04-30 13:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 7:23 [PATCH v2 0/8] gstreamer1.0: 1.12.4 -> 1.14.0 kai.kang
2018-04-25 7:23 ` [PATCH v2 1/8] " kai.kang
2018-04-25 7:23 ` [PATCH v2 2/8] gstreamer1.0-plugins-base: " kai.kang
2018-05-02 3:33 ` Anuj Mittal
2018-05-02 3:40 ` Anuj Mittal
2018-04-25 7:23 ` [PATCH v2 3/8] gstreamer1.0-plugins-bad: " kai.kang
2018-05-02 3:23 ` Anuj Mittal
2018-04-25 7:23 ` [PATCH v2 4/8] gstreamer1.0-plugins-ugly: " kai.kang
2018-04-25 7:23 ` [PATCH v2 5/8] gstreamer1.0-plugins-good: " kai.kang
2018-05-02 3:17 ` Anuj Mittal
2018-05-02 9:26 ` Burton, Ross
2018-04-25 7:23 ` [PATCH v2 6/8] gstreamer1.0-libav: " kai.kang
2018-04-25 7:23 ` [PATCH v2 7/8] gst-validate: " kai.kang
2018-04-25 7:23 ` [PATCH v2 8/8] gstreamer1.0: upgrade other packages to 1.14.0 kai.kang
2018-04-30 12:58 ` Alexander Kanavin [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=d33b20e6-d156-6610-1e12-aac3b0932959@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=kai.kang@windriver.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