Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork cleanup: proposal
Date: Sun, 6 Apr 2014 14:07:15 +0200	[thread overview]
Message-ID: <20140406140715.18d1956c@skate> (raw)
In-Reply-To: <20140329141130.GK3227@free.fr>

Dear Yann E. MORIN,

On Sat, 29 Mar 2014 15:11:30 +0100, Yann E. MORIN wrote:

> On 2014-03-16 08:29 +0100, Thomas De Schampheleire spake thusly:
> > It would certainly be very useful if some contributors would do
> > triaging of patches they care about. It will help reduce the backlog
> > even faster, so yes please!
> > 
> > At the same time, I do think that we need a garbage collector that
> > looks at all remaining patches, even for those he or she does not
> > particularly care about. After all, this is the only way to cleanup
> > the list.
> 
> For the records, Maxime Hadjinlian, Samuel MArtin and I will be meeting
> 2014-04-10 (Thursday in two weeks from now) for a Pathwork party.
> 
> The goal is to spend the whole evening looking at the PAtchwork, and
> apply the triaging as per your proposal in this thread.

As we discussed on IRC, I'll try to be online on Thursday evening to
maybe discuss some patchwork entries and take decisions about them.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-04-06 12:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 20:59 [Buildroot] Patchwork cleanup: proposal Thomas De Schampheleire
2014-03-10 19:39 ` Thomas De Schampheleire
2014-03-15 21:53 ` Yann E. MORIN
2014-03-16  7:29   ` Thomas De Schampheleire
2014-03-29 14:11     ` Yann E. MORIN
2014-04-06 12:07       ` Thomas Petazzoni [this message]
2014-04-13  6:10         ` Thomas De Schampheleire
2014-04-13 14:16           ` Yann E. MORIN
2014-04-13 19: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=20140406140715.18d1956c@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