From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Policy for 'Pending' patches (was Re: [PATCH 02/16] slang: Fix namespace conflict vis-a-vis posix_close)
Date: Thu, 10 Sep 2015 15:08:41 +0300 [thread overview]
Message-ID: <55F172C9.3030601@linux.intel.com> (raw)
In-Reply-To: <55F16E82.1070708@gmail.com>
On 09/10/2015 02:50 PM, Trevor Woerner wrote:
>> Then we can formulate a policy on top of that: for example, if a patch
>> has been 'Pending' for 3 months, the person who added it gets a
>> reminder to update the status; if the patch has been 'Pending' for 6
>> months and the patch person has been unresponsive, no more patches are
>> accepted from that person until he does the upstreaming of the ones he
>> already got into oe-core. Something like that.
>
> With so many maintainers on so many different layers/etc we would need
> some sort of billboard somewhere listing the names of people currently
> on the "naughty" list ;-)
Yes, something similar to http://recipes.yoctoproject.org
And the autobuilder could automatically reject or flag a patch that adds
custom 'Pending' patches, if the patch author is determined to be on the
'naughty' list :-)
Alex
next prev parent reply other threads:[~2015-09-10 12:06 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 23:07 [PATCH 00/16] Recipes fixes for clang Khem Raj
2015-09-08 23:07 ` [PATCH 01/16] irda-utils: Weak Define the build TARGETS Khem Raj
2015-09-08 23:07 ` [PATCH 02/16] slang: Fix namespace conflict vis-a-vis posix_close Khem Raj
[not found] ` <0b794c84466fef2ece1269e01820503b4bce0b52.1441753511.git.raj.khem@gmai l.com>
2015-09-09 10:02 ` alexander.kanavin
2015-09-09 10:23 ` alexander.kanavin
2015-09-09 16:02 ` Khem Raj
2015-09-10 11:21 ` Alexander Kanavin
2015-09-10 11:50 ` Trevor Woerner
2015-09-10 12:06 ` Burton, Ross
2015-09-10 12:08 ` Alexander Kanavin [this message]
2015-09-10 12:12 ` Policy for 'Pending' patches (was Re: [PATCH 02/16] slang: Fix namespace conflict vis-a-vis posix_close) Gary Thomas
2015-09-10 12:12 ` Burton, Ross
2015-09-10 12:15 ` Gary Thomas
2015-09-10 15:22 ` Khem Raj
2015-09-10 18:03 ` alexander.kanavin
2015-09-10 15:37 ` akuster808
2015-09-10 18:06 ` alexander.kanavin
2015-09-08 23:07 ` [PATCH 03/16] sudo: Include sys/types.h for id_t definition Khem Raj
2015-09-08 23:07 ` [PATCH 04/16] man: Use -DSYSV when builing for linux Khem Raj
2015-09-08 23:07 ` [PATCH 05/16] minicom: Fix build with musl Khem Raj
2015-09-08 23:07 ` [PATCH 06/16] bdwgc: Include signal.h instead of hard asm/sigcontext.h Khem Raj
2015-09-08 23:07 ` [PATCH 07/16] ccache: Dont add LDFLAGS to compiler flags Khem Raj
2015-09-08 23:07 ` [PATCH 08/16] latencytop: Fix build with clang Khem Raj
2015-09-08 23:07 ` [PATCH 09/16] alsa-tools: Fix compiling " Khem Raj
2015-09-08 23:07 ` [PATCH 10/16] kexec-tools: Pass -r directly to linker Khem Raj
2015-09-08 23:07 ` [PATCH 11/16] xorg-driver: Fix logical && with bitwise and operation Khem Raj
2015-09-09 7:44 ` Nicolas Dechesne
2015-09-09 7:52 ` Khem Raj
2015-09-09 8:07 ` Nicolas Dechesne
2015-09-09 16:00 ` Nicolas Dechesne
2015-09-09 16:09 ` Khem Raj
2015-09-09 16:08 ` Khem Raj
2015-09-08 23:07 ` [PATCH 12/16] puzzles: Fix build with clang Khem Raj
2015-09-08 23:07 ` [PATCH 13/16] sudo: Disable rsize_t deliberately Khem Raj
2015-09-08 23:07 ` [PATCH 14/16] webkit-gtk: Backport fix to remove FrameDestructionObserver Khem Raj
2015-09-09 13:04 ` Burton, Ross
2015-09-09 19:28 ` Khem Raj
2015-09-09 19:29 ` Burton, Ross
2015-09-08 23:07 ` [PATCH 15/16] mdadm: Fix bugs exposed by clang Khem Raj
2015-09-08 23:07 ` [PATCH 16/16] directfb: Avoid using VLAs and printf formats Khem Raj
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=55F172C9.3030601@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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