From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/7] gstreamer1.0-plugins-base: upgrade to version 1.6.0
Date: Mon, 28 Sep 2015 08:44:10 +0200 [thread overview]
Message-ID: <5608E1BA.2060301@pseudoterminal.org> (raw)
In-Reply-To: <CAMKF1srHAox4XZntPRCC-jzzZDwHtt46UC+ekahKE8s_YzXBpw@mail.gmail.com>
Am 2015-09-28 um 03:07 schrieb Khem Raj:
> On Sun, Sep 27, 2015 at 2:48 PM, Carlos Rafael Giani
> <dv@pseudoterminal.org> wrote:
>> A number of patches had to be deleted in order for the recipe to work.
>>
>> Patches which cannot be applied cleanly to 1.6.0 and are nontrivial to fix:
>> * 0001-basetextoverlay-make-memory-copy-when-video-buffer-s.patch
>> * do-not-change-eos-event-to-gap-event2.patch
>> * do-not-change-eos-event-to-gap-event3.patch
>> * do-not-change-eos-event-to-gap-event-if.patch
>> * handle-audio-video-decoder-error.patch
>> * taglist-not-send-to-down-stream-if-all-the-frame-cor.patch
>>
> has these been dropped ? if so then what do we lose.
We lose nothing that hasn't either been included already or needs to be
reworked anyway.
There are two things I overlooked though:
* The do-not-change-eos-event-to-gap-event* patches aren't needed
anymore, because the authors have sent in a completely different patch,
which has been included in upstream.
* The 0002-gstplaysink-don-t-set-async-of-custom-text-sink-to-f.patch ,
which hasn't been deleted so far, has been rejected by upstream. I
noticed there is a "denied" upstream-status available, but I would
rather delete this patch as well, especially since the discussion in
upstream indicates that this is more i.MX specific. Opinions?
The other patches in the list above, however, need to be reworked to
apply against 1.6.
0001-basetextoverlay-make-memory-copy-when-video-buffer-s.patch has been
rejected by upstream,
handle-audio-video-decoder-error.patch is under discussion.
taglist-not-send-to-down-stream-if-all-the-frame-cor.patch hasn't been
looked at yet by upstream.
Since these no longer apply cleanly against 1.6.0, we anyway have no
option but to delete them and wait until the authors reworked them.
next prev parent reply other threads:[~2015-09-28 6:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 21:48 [PATCH 1/7] gstreamer1.0: upgrade to version 1.6.0 Carlos Rafael Giani
2015-09-27 21:48 ` [PATCH 2/7] gstreamer1.0-plugins-base: " Carlos Rafael Giani
2015-09-28 1:07 ` Khem Raj
2015-09-28 6:44 ` Carlos Rafael Giani [this message]
2015-09-28 6:47 ` Khem Raj
2015-09-28 6:53 ` Carlos Rafael Giani
2015-09-28 7:02 ` Khem Raj
2015-09-27 21:48 ` [PATCH 3/7] gstreamer1.0-plugins-good: " Carlos Rafael Giani
2015-10-26 17:25 ` Burton, Ross
2015-09-27 21:48 ` [PATCH 4/7] gstreamer1.0-plugins-bad: " Carlos Rafael Giani
2015-10-26 17:20 ` Burton, Ross
2015-10-27 14:10 ` Carlos Rafael Giani
2015-10-30 18:54 ` Andre McCurdy
2015-11-02 16:56 ` Saul Wold
2015-09-27 21:48 ` [PATCH 5/7] gstreamer1.0-plugins-ugly: " Carlos Rafael Giani
2015-09-27 21:48 ` [PATCH 6/7] gstreamer1.0-libav: " Carlos Rafael Giani
2015-09-27 21:48 ` [PATCH 7/7] gstreamer1.0-rtsp-server: " Carlos Rafael Giani
2015-09-28 9:17 ` [PATCH 1/7] gstreamer1.0: " Burton, Ross
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=5608E1BA.2060301@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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