From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] vala: add vala/valac wrapper
Date: Tue, 23 Feb 2016 16:19:42 +0100 [thread overview]
Message-ID: <87wppv78tt.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20160223104816.20c97306@free-electrons.com> (Thomas Petazzoni's message of "Tue, 23 Feb 2016 10:48:16 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Hello,
> On Tue, 23 Feb 2016 10:42:24 +0100, Arnout Vandecappelle wrote:
>> This could indeed be a good idea. One reason to limit the number of committers
>> was to avoid conflicts (i.e. two committers working on the same patch in
>> parallel), but as I understand it, Thomas and Peter noticed that this isn't
>> really a problem in practice.
>>
>> So indeed, having a third person that applies trivial patches could be
>> worthwhile to try.
>>
>> That said, Yann and I are already spending a large part of our buildroot time
>> on reviewing patches. I don't think that applying them immediately is going to
>> make that much of a difference.
> Fully agreed: applying the patch is clearly not what takes time. It's a
> mechanical and stupid operation.
Agreed. I'm all for ways of improving our ways of working, but I don't
think this will change much. Adding Thomas as a co-maintainer has imho
been very good, but adding a 3rd committer without having more reviewers
imho won't make any significant difference.
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2016-02-23 15:19 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 [this message]
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=87wppv78tt.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 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.