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] [PATCH 1/3] vala: add vala/valac wrapper
Date: Tue, 23 Feb 2016 10:10:20 +0100	[thread overview]
Message-ID: <20160223101020.0a87c0f3@free-electrons.com> (raw)
In-Reply-To: <56CBA547.3020200@zacarias.com.ar>

Hello Gustavo,

On Mon, 22 Feb 2016 21:18:15 -0300, Gustavo Zacarias wrote:

> I was asked to step in and maintain webkitgtk, gtk3 & accesory packages.
> And this has been sitting in patchwork for quite some time with no 
> comments or anything and rotting down (this = the gtk3 bump and other 
> pieces that depend on it).
> It means i'll just take is as there's no interest and just leave it rot 
> completely - i didn't pick this up because it's something i use or have 
> any particular interest in.
> If you're implying i don't help in other aspects and i just care about 
> what i send i suggest you take a look at lots of autobuilder fixes for 
> packages i never use.

As Arnout said, all our patches are definitely appreciated, and most of
them are applied really quickly. Some of them indeed take more time,
but there's nothing personal against you: we have ~300 other patches
sitting in patchwork.

However, you are almost never helping us by reviewing/testing patches
from others. Due to this, instead of applying your patches, I have to
review and test patches from other contributors. Conclusion: if you
want your patches to be applied faster, the best way is to help the
community by reviewing and testing patches. Your review and test effort
would be really valuable: you are a long-time Buildroot developer, so
you know all the best practices, usual pitfalls and all, which means
that we trust your review.

Thanks a lot!

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

  parent reply	other threads:[~2016-02-23  9:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 16:01 [Buildroot] [PATCH 1/3] vala: add vala/valac wrapper Gustavo Zacarias
2016-02-02 16:01 ` [Buildroot] [PATCH 2/3] libgee: new package Gustavo Zacarias
2016-02-02 16:01 ` [Buildroot] [PATCH 3/3] granite: " Gustavo Zacarias
2016-02-21 21:28 ` [Buildroot] [PATCH 1/3] vala: add vala/valac wrapper Thomas Petazzoni
2016-02-22  1:22   ` Gustavo Zacarias
2016-02-22 23:47     ` Arnout Vandecappelle
2016-02-23  0:18       ` Gustavo Zacarias
2016-02-23  0:40         ` Arnout Vandecappelle
2016-02-23  1:06           ` Gustavo Zacarias
2016-02-23  9:42             ` Arnout Vandecappelle
2016-02-23  9:48               ` Thomas Petazzoni
2016-02-23 15:19                 ` Peter Korsgaard
2016-02-23 19:43                 ` Arnout Vandecappelle
2016-02-23 20:58                   ` Thomas Petazzoni
2016-02-23  9:10         ` Thomas Petazzoni [this message]
2016-02-22 23:48 ` Arnout Vandecappelle
2016-02-23  0:27   ` Gustavo Zacarias
2016-02-23  0:30     ` Arnout Vandecappelle

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=20160223101020.0a87c0f3@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