From: Jeff Bailey <jbailey@raspberryginger.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Let core developers "vote" to accept patches.
Date: Mon, 21 Aug 2006 06:14:33 -0700 [thread overview]
Message-ID: <20060821131433.GA22729@titanium.v3.ca> (raw)
In-Reply-To: <871wrjhrks.fsf@night.trouble.net>
On Tue, Aug 15, 2006 at 12:37:23AM +0200, Johan Rydberg wrote:
> In other projects that I've worked on, we've used a system where the
> core developers can either give a +1 or a -1 on a contributed patch.
> If a patch receives two +1's or more, it is accepted (if there are no
> -1's) and committed by one of the developers.
Do the core devs and maintainers not feel empowered to just commit the
patch if they would otherwise +1 it? It seems like grub is a
sufficiently small project that moves sufficiently slowly that rolling
back a contentious patch would be easier than any sort of beaurocratic
overhead.
Tks,
Jeff Bailey
--
I do not agree with a word you say, but I will defend to the death your
right to say it.
- Voltaire
prev parent reply other threads:[~2006-08-21 13:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 22:37 Let core developers "vote" to accept patches Johan Rydberg
2006-08-15 0:27 ` Hollis Blanchard
2006-08-15 9:20 ` Marco Gerards
2006-08-15 12:42 ` Yoshinori K. Okuji
2006-08-15 13:26 ` Johan Rydberg
2006-08-21 13:14 ` Jeff Bailey [this message]
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=20060821131433.GA22729@titanium.v3.ca \
--to=jbailey@raspberryginger.com \
--cc=grub-devel@gnu.org \
/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.