From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: include default PR or not
Date: Sat, 23 Jan 2010 22:11:55 +0100 [thread overview]
Message-ID: <hjfon5$59s$1@ger.gmane.org> (raw)
In-Reply-To: <1264114415.457.1069.camel@lenovo.internal.reciva.com>
Phil Blundell wrote:
> I'm not entirely sure what point you are making about it being
> undesirable for the TSC to "rule in favour of one or the other faction".
I'm not advocating for the TSC to take a soft stance for fear of
confrontation. But why have a rule about something that isn't really so
important? If we follow down the path of letting the TSC decide even
over silly things like PR, I'm afraid two things will happen. One is
the TSC will become overloaded and two OE will become a bureaucratic,
no-fun hell. Not sure that would be an improvement.
next prev parent reply other threads:[~2010-01-23 21:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 20:32 [PATCH] barebox: Add recipe for this new bootloader Eric Benard
2010-01-17 20:51 ` Eric Bénard
2010-01-17 21:02 ` Koen Kooi
2010-01-17 21:28 ` Paul Menzel
2010-01-17 21:50 ` [PATCH] usermanual : update note about PR Eric Benard
2010-01-17 22:11 ` Frans Meulenbroeks
2010-01-18 9:24 ` Eric Bénard
2010-01-18 16:03 ` Rolf Leggewie
2010-01-18 0:31 ` Rolf Leggewie
2010-01-17 21:53 ` [PATCH] barebox: Add recipe for this new bootloader Frans Meulenbroeks
2010-01-17 23:06 ` Mike Westerhof
2010-01-18 0:22 ` Rolf Leggewie
2010-01-18 13:10 ` Phil Blundell
2010-01-18 14:28 ` Richard Purdie
2010-01-18 16:24 ` include default PR or not (was: [PATCH] barebox: Add recipe for this new bootloader) Rolf Leggewie
2010-01-21 22:53 ` Phil Blundell
2010-01-22 7:52 ` Frans Meulenbroeks
2010-01-22 16:13 ` Khem Raj
2010-01-24 10:20 ` include default PR or not Koen Kooi
2010-01-23 21:11 ` Rolf Leggewie [this message]
2010-01-19 20:44 ` [PATCH] barebox: Add recipe for this new bootloader Eric Bénard
2010-01-21 23:07 ` 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='hjfon5$59s$1@ger.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--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.