From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] review process
Date: Fri, 27 Aug 2010 06:29:40 -0600 [thread overview]
Message-ID: <4C77AFB4.6000809@mlbassoc.com> (raw)
In-Reply-To: <4C77AE8B.80607@xora.org.uk>
On 08/27/2010 06:24 AM, Graeme Gregory wrote:
> On 27/08/10 13:15, Frans Meulenbroeks wrote:
>> 1. If a patch does not get any review feedback in X weeks time; it is
>> ok to apply it. People who need more time to review a patch can
>> mention that in a short reply. In that case they are granted Y more
>> weeks to review.
>> (suggestion: X = Y = 2)
> I have always been a supported of apply it and see who screams. I have
> suggested before that after 2 weeks without review any non core patch is
> obviously OK.
That said, what good does it do for those affected to scream if
the originator simply ignores it??
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-08-27 12:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 12:15 [RFC] review process Frans Meulenbroeks
2010-08-27 12:24 ` Graeme Gregory
2010-08-27 12:29 ` Gary Thomas [this message]
2010-08-27 12:33 ` Frans Meulenbroeks
2010-08-27 12:37 ` Dr. Michael Lauer
2010-08-27 13:46 ` Execution of Build Output Failing (Testing) openembedded
2010-08-27 17:41 ` Khem Raj
2010-08-27 19:37 ` openembedded
2010-08-27 15:11 ` [RFC] review process Roman I Khimov
2010-08-28 10:25 ` Koen Kooi
2010-08-28 12:17 ` Frans Meulenbroeks
2010-09-06 18:54 ` Frans Meulenbroeks
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=4C77AFB4.6000809@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-devel@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 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.