From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] List of pending patches: what to do?
Date: Wed, 31 Jul 2013 19:18:25 +0200 [thread overview]
Message-ID: <20130731191825.5b7377e9@skate> (raw)
In-Reply-To: <20130731191415.545f7dff@skate>
On Wed, 31 Jul 2013 19:14:15 +0200, Thomas Petazzoni wrote:
> http://patchwork.ozlabs.org/patch/181870 [1/9] firefox: host-python dependency needs --enable-unicodedata
> http://patchwork.ozlabs.org/patch/181871 [2/9] firefox: valgrind dependency needs --enable-tls for debug build
> http://patchwork.ozlabs.org/patch/181874 [3/9] firefox: sqlite dependency needs new compile-time options
> http://patchwork.ozlabs.org/patch/181872 [4/9] firefox: installing default extensions needs host-xmlstarlet dependency
> http://patchwork.ozlabs.org/patch/181875 [5/9] firefox: installing default extensions needs host-unzip dependency
> http://patchwork.ozlabs.org/patch/181877 [6/9] firefox: Mozilla Web Browser
> http://patchwork.ozlabs.org/patch/181876 [7/9] firefox: GNU gnash flash plugin needs agg dependency
> http://patchwork.ozlabs.org/patch/181873 [8/9] firefox: GNU gnash flash plugin needs gconf dependency
> http://patchwork.ozlabs.org/patch/181878 [9/9] firefox: GNU gnash flash, an open source Adobe Flash player & plugin
I'm proposing to drop those patches. The patches are from September
2012, and I asked Stefan Froberg in May 2013 whether he was still
interested
(http://lists.busybox.net/pipermail/buildroot/2013-May/071410.html),
and I've got a private answer that said:
"""
Well, those patches were for Firefox version 11.0 so it's quite old
already.
I have a patches for Firefox 16.0 & Firefox 18.0 done but as I
understand it Firefox is never
going to be included in buildroot so I did not post them.
And I have now also unsubscripted from mailing list so I can't post them
even if
someone would like to check them.
So, yeah. Those patches can be wiped out.
If someone from the list still want's them they can be found from
http://binarytouch.com/patches/
(I will put all the rest of my buildroot patches later there after I
have completed my current project)
"""
So unless anyone objects and steps up to refresh and resubmit those
patches, I'm proposing to mark those patches as rejected.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-07-31 17:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 17:14 [Buildroot] List of pending patches: what to do? Thomas Petazzoni
2013-07-31 17:18 ` Thomas Petazzoni [this message]
2013-07-31 20:44 ` Yann E. MORIN
2013-08-01 5:39 ` Thomas Petazzoni
2013-07-31 17:51 ` Gustavo Zacarias
2013-08-01 5:50 ` Thomas Petazzoni
2013-07-31 20:45 ` Thomas De Schampheleire
2013-07-31 20:57 ` Yann E. MORIN
2013-08-01 5:59 ` Thomas Petazzoni
2013-08-01 20:24 ` Yann E. MORIN
2013-07-31 20:55 ` Yann E. MORIN
2013-08-01 6:04 ` Thomas Petazzoni
2013-07-31 22:13 ` Samuel Martin
2013-07-31 22:20 ` Yann E. MORIN
2013-08-01 16:23 ` Thomas Petazzoni
2013-08-01 21:30 ` Samuel Martin
2013-08-02 8:33 ` Thomas De Schampheleire
2013-08-02 8:50 ` Thomas Petazzoni
2013-08-02 9:09 ` Thomas De Schampheleire
2013-08-02 9:10 ` Thomas Petazzoni
2013-08-02 9:27 ` Thomas De Schampheleire
2013-08-12 21:01 ` Arnout Vandecappelle
2013-08-01 2:52 ` Danomi Manchego
2013-08-01 6:13 ` Thomas Petazzoni
2013-08-01 20:14 ` Yann E. MORIN
2013-08-01 6:54 ` Simon Dawson
2013-08-01 7:41 ` Thomas Petazzoni
2013-08-01 16:16 ` Thomas Petazzoni
2013-08-02 8:10 ` Jérôme Pouiller
2013-08-02 11:11 ` Patrick Ziegler
2013-08-02 11:17 ` Thomas Petazzoni
2013-08-19 10:35 ` Luca Ceresoli
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=20130731191825.5b7377e9@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