From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot patchwork: decision on the 10 oldest patches, week 1
Date: Sun, 6 Oct 2013 16:42:27 +0200 [thread overview]
Message-ID: <20131006164227.0ab2a172@skate> (raw)
Hello,
The oldest patches in patchwork don't get a lot of attention (or even
any attention at all). I had a discussion this week with Thomas De
Schampheleire, and we would like to progressively clean up the backlog
of patches we have in patchwork, especially the oldest one.
So, every week, I'll be posting the list of the 10 oldest patches, with
the original patch contributors in Cc. During one week, we have the
opportunity to discuss the patch, whether it is still necessary or not,
how it should be changed to be merged.
In particular, I'm interested in knowing if the original contributor is
still interested by the patch, or if someone else is interested in
adopting the patch and sending an updated version, or if the patch no
longer makes sense due to other changes made in Buildroot.
All patches that have not received any comment or attention within the
week will be removed from patchwork. This is aggressive, but we have
patches sitting in patchwork since one year and half, and this cannot
work.
So, for this first week, the patches are:
1 New: add lava-test package
http://patchwork.ozlabs.org/patch/155498/
ludovic.desroches at atmel.com
2 [v3] busybox: install S41inetd and inetd.conf if inetd is enabled in busybox.
http://patchwork.ozlabs.org/patch/164551/
keguang.zhang at gmail.com
3 [1/1] ccache: expose control interface via 'make ccache-options'
http://patchwork.ozlabs.org/patch/165382/
roylee17 at gmail.com
4 [V2] p910nd: Add p910nd lightweight printserver
http://patchwork.ozlabs.org/patch/165542/
david.c.purdy at gmail.com
5 Added package v86d which provides a real-mode helper for uvesafb driver.
http://patchwork.ozlabs.org/patch/171840/
golubovsky at gmail.com
6 grub: fix stage2 link with recent binutils
http://patchwork.ozlabs.org/patch/173191/
net147 at gmail.com
7 valgrind: valgrind/valgrind.h missing if --disable-tls enabled
http://patchwork.ozlabs.org/patch/176795/
stefan.froberg at petroprogram.com
8 [2/2] rdiff-backup: new package
http://patchwork.ozlabs.org/patch/176956/
avishorp at gmail.com
9 [1/2,v4] package: pkg-generic: Support building override source without copying in common package infrastructure.
http://patchwork.ozlabs.org/patch/177618/
sonic.adi at gmail.com
10 grub: add host support
http://patchwork.ozlabs.org/patch/177705/
rbraun at sceen.net
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next reply other threads:[~2013-10-06 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 14:42 Thomas Petazzoni [this message]
2013-10-08 15:17 ` [Buildroot] Buildroot patchwork: decision on the 10 oldest patches, week 1 Ludovic Desroches
2013-10-09 9:34 ` [Buildroot] [PATCH] New: add lava-test package ludovic.desroches at atmel.com
2013-10-09 11:55 ` Thomas Petazzoni
2013-10-09 14:42 ` Ludovic Desroches
2013-10-11 8:11 ` [Buildroot] Buildroot patchwork: decision on the 10 oldest patches, week 1 Thomas De Schampheleire
2013-10-13 21:18 ` Arnout Vandecappelle
2013-11-01 8:07 ` Thomas De Schampheleire
2013-11-01 9:57 ` Gustavo Zacarias
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=20131006164227.0ab2a172@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