From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] FEATURES use or misuse?
Date: Tue, 3 Nov 2009 22:26:24 +0000 [thread overview]
Message-ID: <20091103222624.19d4b591@snowcone> (raw)
In-Reply-To: <200911032304.58321.patrick@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]
On Tue, 3 Nov 2009 23:04:58 +0100
Patrick Lauer <patrick@gentoo.org> wrote:
> > If you want to fix PMS, then send a patch
> I tried, and as I've been saying for a long time they get rejected.
Yes, let's look at the patches that you sent that were rejected:
The first was one where you asked the PMS team to make a change that
goes directly against a Council decision, and that the PMS team does
not have the authority to accept on its own. You were told to bring
the issue to gentoo-dev@ for further attention. You never did.
The second patch you sent:
* incorrectly removed as "no content" two sentences that had specific
and necessary meaning.
* didn't apply against any version of PMS except your much-modified
local version, and that didn't make sense when applied to version of
PMS that anyone else had.
Again, no updated patch was sent.
The third patch you sent had a number of small issues and could have
been improved. You did not send an updated patch with those issues
fixed.
> Funnily not by any dev but by some random user, but who cares :)
Everyone on the PMS mailing list is more than welcome to do patch
reviews. The more eyes we have looking at things the better. Policy is
not to apply patches until everyone is happy with them; objections are
considered on their merits, not on their author.
Every other person who has had people comment upon a patch they
submitted has either addressed the issues and submitted an updated
patch, or explained why they feel the patch is correct as-is.
Every other person who has submitted a patch has worked with all the
reviewers to reach a conclusion that is acceptable to all involved.
Every other person has an ultimate patch acceptance rate of at least
98%. You are the *only* person to have had patches rejected where the
submitter did not agree with the rejection.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-11-03 22:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 15:48 [gentoo-dev] FEATURES use or misuse? Patrick Lauer
2009-11-03 17:27 ` Sebastian Pipping
2009-11-03 20:36 ` Patrick Lauer
2009-11-03 20:58 ` Ciaran McCreesh
2009-11-03 22:28 ` Patrick Lauer
2009-11-04 0:11 ` [gentoo-dev] " Ryan Hill
2009-11-04 8:26 ` Patrick Lauer
2009-11-05 1:36 ` Ryan Hill
2009-11-05 4:56 ` [gentoo-dev] a pragmatic approach to FEATURES [was FEATURES use or misuse?] Brian Harring
2009-11-05 8:49 ` Thilo Bangert
2009-11-05 9:36 ` Brian Harring
2009-11-08 9:21 ` Thilo Bangert
2009-11-03 21:26 ` [gentoo-dev] FEATURES use or misuse? Alexis Ballier
2009-11-03 22:04 ` Patrick Lauer
2009-11-03 22:26 ` Ciaran McCreesh [this message]
2009-11-04 0:33 ` Sebastian Pipping
2009-11-04 8:26 ` Patrick Lauer
2009-11-03 23:04 ` David Leverton
2009-11-04 1:31 ` [gentoo-dev] " Duncan
2009-11-04 22:12 ` Peter Hjalmarsson
2009-11-05 5:04 ` Brian Harring
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=20091103222624.19d4b591@snowcone \
--to=ciaran.mccreesh@googlemail.com \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox