All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] vala: add vala/valac wrapper
Date: Mon, 22 Feb 2016 22:06:57 -0300	[thread overview]
Message-ID: <56CBB0B1.6020506@zacarias.com.ar> (raw)
In-Reply-To: <56CBAA86.4070305@mind.be>

On 22/02/16 21:40, Arnout Vandecappelle wrote:

>> 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.
>
>   That's why I mentioned that 92% of the patches you submitted have already been
> applied. The other buildroot contributors really appreciate the work you do. And
> share your frustration that too many patches tend to linger, and need to be
> rebased all the time. In fact, Thomas and Peter have the additional frustration
> that all of their time is taken up by applying other people's patches, leaving
> no time to work on their own ideas.

Oh come on, you're smarter than that: most of my merged patches are trivial.
That's the consequence of let's call them "big series" lingering on 
forever - it really demotivates to work on anything groundbreaking since 
you've gotta rebase forever to keep them sane on top of other changes 
with nothing happening to it.
How about relinquising some control? Add a new committer, maybe Yann, 
yourself or some other trusted volunteer, that way the new committer(s) 
can clean up the simple queue and leave the more contentious series for 
the more experienced ones. Maybe put on some simple ground rules like 
don't commit your own stuff and so on.
They will make mistakes, sure, but then everybody does and both Peter & 
Thomas will get some free time for their particular interests.
Otherwise we end up with these emails that make a lot of noise and then 
everything cools down and nothing changes, the scaling remains at the 
same sucklevel.
It's not a life-forever thing, if it doesn't work then try some other 
thing, but if there's no trying for some new approach evidently nothing 
will change no matter how much you push for new blood, reviews, tested 
and acks.
Regards.

  reply	other threads:[~2016-02-23  1:06 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 [this message]
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
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=56CBB0B1.6020506@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.