Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nathaniel Roach <nroach44@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Proposal to remove patches from patchwork, or find adopters
Date: Thu, 07 May 2015 16:21:18 +0800	[thread overview]
Message-ID: <554B207E.7050608@gmail.com> (raw)
In-Reply-To: <20150506235353.7740a9d3@free-electrons.com>

Apologies Thomas, it's assignment season and I brushed off your first email.

RE my patch (package/systemd: journald should use volatile storage):
The bug it works around (#7892) as far as I can tell, is still an issue.

I'd prefer that the patch remains as a work around for the issue, but it 
isn't a big deal either way, and is your call.

I've updated the bug with the details discussed in IRC a while ago.

On 07/05/15 05:53, Thomas Petazzoni wrote:
> Hello,
>
> On April 21th, I sent a personal reminder to all the patch authors who
> had patches older than 15 days pending in Buildroot's patchwork.
>
> Since then, a number of authors have responded to indicate whether they
> are still interested or not by their patches, which is great.
>
> However, a fairly significant portion of the patches have not been
> given any feedback by their respective authors. I have triaged the
> answers from the authors, and classified such patches. The list of such
> patches follows. Note that the authors of such patches are again added
> in the To: field of this e-mail, to get their attention.
>
> I hereby propose to mark all those patches as "Rejected" on May 21 (i.e
> one month after the reminder), if the authors still haven't expressed
> interest and nobody else volunteered to adopt the patch. I believe we
> can't keep for months or years patches that the original author has
> lost interest in, and nobody else seems to be interested in.
>
> Let me know if you agree or disagree with this proposal.
>
> Volunteers interested in adopting one or several of the below patches,
> please speak up.
>
> Here is the list of such patches:
--snip--
>
> Thanks,
>
> Thomas Petazzoni
>

  parent reply	other threads:[~2015-05-07  8:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 21:53 [Buildroot] Proposal to remove patches from patchwork, or find adopters Thomas Petazzoni
2015-05-06 22:10 ` Alexey Brodkin
2015-05-06 22:52 ` Emeric Vigier
2015-05-06 23:59 ` Jeremy Kerr
2015-05-07  3:42 ` Baruch Siach
2015-05-07  5:48 ` Bernd Kuhls
2015-05-07  6:54 ` jordi montagne
2015-05-11 14:25   ` jean burgat
2015-05-07  8:13 ` Jérôme Pouiller
2015-05-07  8:21 ` Nathaniel Roach [this message]
2015-05-07  9:34 ` Károly Kasza
2015-05-07  9:45 ` Will Wagner
2015-05-07 10:19 ` Samuel Martin
2015-05-07 10:30   ` Thomas Petazzoni
2015-05-07 11:14 ` Carlos Santos
2015-05-15 18:28   ` Carlos Santos
2015-05-15 20:14     ` Carlos Santos
2015-05-16  8:37       ` Thomas Petazzoni
2015-05-08  1:20 ` Zhangjian
2015-05-08 13:42 ` Maxime Hadjinlian
2015-05-10 10:00 ` Thomas De Schampheleire
2015-05-29 15:08   ` Thomas De Schampheleire
2015-05-11 15:11 ` Steve Calfee

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=554B207E.7050608@gmail.com \
    --to=nroach44@gmail.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