From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork oldest patches cleanup #4 (deadline January 5)
Date: Mon, 6 Jan 2014 13:05:03 +0800 [thread overview]
Message-ID: <20140106130503.2df2a9ef@skate> (raw)
In-Reply-To: <CAAXf6LVVi6d=xRjsqW8eSMAf1CpKyU-qUTQ2dbfCPU=EF__jcA@mail.gmail.com>
Dear Thomas De Schampheleire,
On Sun, 5 Jan 2014 11:21:33 +0100, Thomas De Schampheleire wrote:
> > libatomic_ops version update 7.3alpha2 old version 1.2 does not
> > compiles with modern gcc and utils
> > Alexander Khryukin <alexander@mezon.ru>
> > http://patchwork.ozlabs.org/patch/198133
>
> No feedback, marked as rejected.
I think bumping the version of a package is often useful, so I'm not
sure I would mark this patch as rejected. Or if no one is pushing to
bump libatomic_ops, then we should just assume no one cares, and
therefore there's no point in keeping the patch around?
> > [07/10] libffi: make thread support optional
> > Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > http://patchwork.ozlabs.org/patch/199883
>
> No feedback, marked as rejected.
It's weird because I don't see libffi build failures in the
autobuilders, even though there is one no thread ARM toolchain in the
configurations.
> > [4/4] gstreamer: replace gst-ffmpeg with gst-libav
> > bogdan at nimblex.org
> > http://patchwork.ozlabs.org/patch/207431
>
> No feedback, rejected.
I'm a little bit concerned about how we reject patches here. Maybe
replacing gst-ffmpeg by gst-libav makes sense and should be done? If we
don't keep the patch around, we'll have no way to remember that it
should be done at some point in the future. I admit that by doing
this, we'll never shrink the list of pending patches, but I have the
feeling that we might be missing useful ideas.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-06 5:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 20:46 [Buildroot] Patchwork oldest patches cleanup #4 (deadline January 5) Thomas De Schampheleire
2013-12-22 21:00 ` Yann E. MORIN
2013-12-23 7:51 ` Thomas Petazzoni
2013-12-23 8:11 ` Thomas De Schampheleire
2013-12-23 12:18 ` François Perrad
2013-12-23 14:20 ` Thomas De Schampheleire
2014-01-05 10:21 ` Thomas De Schampheleire
2014-01-05 10:23 ` Thomas De Schampheleire
2014-01-06 5:05 ` Thomas Petazzoni [this message]
2014-01-06 10:16 ` Thomas De Schampheleire
2014-01-06 10:48 ` Bogdan Radulescu
2014-01-20 15:48 ` Thomas De Schampheleire
2014-01-20 20:28 ` Thomas De Schampheleire
2014-01-25 11:50 ` Bogdan Radulescu
2014-01-27 8:11 ` Thomas De Schampheleire
2014-01-20 15:58 ` Thomas De Schampheleire
2014-01-28 17:00 ` Thomas Petazzoni
2014-02-03 9:15 ` Thomas De Schampheleire
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=20140106130503.2df2a9ef@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox