From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [poky][PATCH v4 0/2] gstreamer1.0: Add patches for Gstreamer 1.4.5
Date: Sat, 22 Aug 2015 00:02:48 +0200 [thread overview]
Message-ID: <55D7A008.5010501@pseudoterminal.org> (raw)
In-Reply-To: <CAP9ODKqcyRt_Yc=aO=7dN0hreYnwHXOEE-FiuSbG0dPDqecMVQ@mail.gmail.com>
Am 2015-08-22 um 00:01 schrieb Otavio Salvador:
> On Fri, Aug 21, 2015 at 6:57 PM, Carlos Rafael Giani
> <dv@pseudoterminal.org> wrote:
>> These are backports, so I do not see a problem with them. However, keep in
>> mind that GStreamer 1.6 will be out in a few days, so I recommend hold off
>> any patches that are not backports. I have recipes prepared for 1.5.90 (=
>> 1.6 release candidate) that I will then send to the mailing list. New
>> patches should be applied on top of that, not 1.4.5.
> In this case it is better to not merge those and wait for 1.5.90 to be
> send. This allow for testing and also FSL checking for any other
> pending fixes.
>
>
Yes. In fact, several of the present non-backport patches no longer
apply. I had to delete them because fixing them was a nontrivial task,
and should better be done by the original authors. I already sent a
heads up about this to them.
next prev parent reply other threads:[~2015-08-21 22:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 14:29 [poky][PATCH v4 0/2] gstreamer1.0: Add patches for Gstreamer 1.4.5 Yuqing Zhu
2015-08-21 14:29 ` [poky][PATCH v4 1/2] gstreamer1.0: Fix ticky events haven't been sent out when active track reach EOS Yuqing Zhu
2015-08-21 14:29 ` [poky][PATCH v4 2/2] gstreamer1.0: Fix QoS/lateness checking if subclass implements prepare/prepare_list vfuncs Yuqing Zhu
2015-08-21 21:11 ` Otavio Salvador
2015-08-21 21:57 ` [poky][PATCH v4 0/2] gstreamer1.0: Add patches for Gstreamer 1.4.5 Carlos Rafael Giani
2015-08-21 22:01 ` Otavio Salvador
2015-08-21 22:02 ` Carlos Rafael Giani [this message]
2015-09-08 8:02 ` Zhu Carol
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=55D7A008.5010501@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
/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.