From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 6/6] libvpx: new package libvpx
Date: Thu, 9 May 2013 23:49:08 +0200 [thread overview]
Message-ID: <20130509234908.797dfc45@skate> (raw)
In-Reply-To: <1368132677-1261-6-git-send-email-spenser@gillilanding.com>
Dear Spenser Gilliland,
On Thu, 9 May 2013 15:51:17 -0500, Spenser Gilliland wrote:
> package/multimedia/Config.in | 1 +
> package/multimedia/gst-plugins-good1/Config.in | 4 ++
> .../gst-plugins-good1/gst-plugins-good1.mk | 10 +++-
The gst-plugins-good1 changes should be in a separate patch from the
patch...
> package/multimedia/libvpx/Config.in | 6 +++
> package/multimedia/libvpx/libvpx.mk | 52 ++++++++++++++++++++
...introducing the libvpx package.
So, first a patch introducing libvpx, and then a patch adding support
for it in gst-plugins-good1.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-05-09 21:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 20:51 [Buildroot] [PATCH v2 1/6] gstreamer1: Add gstreamer version 1.0.7 package Spenser Gilliland
2013-05-09 20:51 ` [Buildroot] [PATCH v2 2/6] gst-plugins-base1: add gstreamer1 base plugins Spenser Gilliland
2013-05-09 20:51 ` [Buildroot] [PATCH v2 3/6] gst-plugins-good1: add gstreamer1 good plugins Spenser Gilliland
2013-05-09 20:51 ` [Buildroot] [PATCH v2 4/6] gst-plugins-bad1: add gstreamer1 bad plugins Spenser Gilliland
2013-05-09 20:51 ` [Buildroot] [PATCH v2 5/6] gst-plugins-ugly1: add gstreamer1 ugly plugins Spenser Gilliland
2013-05-09 20:51 ` [Buildroot] [PATCH v2 6/6] libvpx: new package libvpx Spenser Gilliland
2013-05-09 21:49 ` 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=20130509234908.797dfc45@skate \
--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 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.