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] Worried about patches not being merged?
Date: Fri, 20 Mar 2015 16:37:50 +0100	[thread overview]
Message-ID: <20150320163750.745ba46c@free-electrons.com> (raw)
In-Reply-To: <1426865596.27254.23.camel@embedded.rocks>

J?rg,

On Fri, 20 Mar 2015 16:33:16 +0100, J?rg Krause wrote:

> To be honest, I'm only looking for packages I'm currently using or which
> seems to be interesting to me. I must confess I don't have the time to
> review/test patches I don't care about or which looks to complex.

Yes, this is fine: if everyone takes care of patches touching packages
he is interested in, it would already help a lot.

For example, there are many systemd patches waiting for someone
knowledgeable in systemd stuff to look at them. We used to have Eric Le
Bihan taking care of such patches, but he is no longer active.
Fortunately, Mike Williams and Steven Noonan have appeared and seem to
be interested in systemd, which is great!

> Following the mailing list for some months now I noticed that there is a
> team of five to ten main contributers which do the most reviews and
> tests.

Correct, but as you can see by looking at the patch queue, it's not
enough.

> Maybe a section in the documentation  

Incomplete sentence?

> I think patches should be classified as you mentioned in another mail. I
> like the idea have having tags like "infrastructure", "new package",
> "version bump", ..., to get a quick overview.

True, but on the other hand, someone will have to add those tags
manually for each patch.

Thanks,

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

  reply	other threads:[~2015-03-20 15:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 22:21 [Buildroot] Worried about patches not being merged? Thomas Petazzoni
2015-03-18 20:01 ` Jörg Krause
2015-03-19  8:20   ` Thomas Petazzoni
2015-03-20 15:33     ` Jörg Krause
2015-03-20 15:37       ` Thomas Petazzoni [this message]
2015-03-19  8:35   ` Angelo Compagnucci
2015-03-19  9:16     ` Thomas Petazzoni
2015-03-19  9:34       ` Angelo Compagnucci
2015-03-19 10:25         ` Angelo Compagnucci
2015-03-19 10:26         ` Thomas Petazzoni
2015-03-19 10:45           ` Angelo Compagnucci
2015-03-19 11:09             ` Thomas Petazzoni
2015-03-19 22:27               ` Angelo Compagnucci
2015-03-20 16:02                 ` Thomas Petazzoni

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=20150320163750.745ba46c@free-electrons.com \
    --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