From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] Worried about patches not being merged?
Date: Wed, 18 Mar 2015 21:01:06 +0100 [thread overview]
Message-ID: <1426708866.1395.8.camel@embedded.rocks> (raw)
In-Reply-To: <20150304232101.437af48f@free-electrons.com>
Dear Thomas,
On Mi, 2015-03-04 at 23:21 +0100, Thomas Petazzoni wrote:
> Hello,
>
> If you're worried about patches not being merged, or taking too long to
> get merged, here is a quick statistic I made.
>
> On http://patchwork.ozlabs.org/project/buildroot/list/, on a total of
> 356 pending patches at the time of my testing, only 22 patches had a
> Acked-by, Reviewed-by or Tested-by tag. All of the other 334 patches
> have not been given any of these tags.
>
> If you would like to help getting patches merged more quickly, then
> please help by reviewing and testing patches!
Are there any guidelines for reviewing? It's a pitty that GSoC did not
accepted Buildroot this year. The testing scripts would be a nice
feature.
next prev parent reply other threads:[~2015-03-18 20:01 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 [this message]
2015-03-19 8:20 ` Thomas Petazzoni
2015-03-20 15:33 ` Jörg Krause
2015-03-20 15:37 ` Thomas Petazzoni
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=1426708866.1395.8.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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