From: Holger Freyther <holger+oe@freyther.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: TSC Meetings for the meeting of June
Date: Wed, 30 Jun 2010 21:19:38 +0800 [thread overview]
Message-ID: <4C2B446A.5040301@freyther.de> (raw)
In-Reply-To: <i0f8ct$acp$1@dough.gmane.org>
On 06/30/2010 07:05 PM, Koen Kooi wrote:
>
> What about tackling the items from the previous month first before going
> off on this cosmetic change that wasn't even discussed in the community
> first before the TSC jumped the gun on it?
Well,
what do you want to say with was not discussed? We would not have picked
up the topic when it was not discussed in the community as we are not
making up topics.
And rest assured personally for a non native english speaker master,
foobar, blabla has about the same semantic for a branch name (I get used
to any of those), for the native ones this was a pretty big issue...
In regard to the TSC, what mode of operation do you propose? We freeze
the tree until all items are implemented in the order they are proposed?
We find people driving a topic?
next prev parent reply other threads:[~2010-06-30 13:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 13:03 TSC Meetings for the meeting of June Holger Freyther
2010-06-09 13:25 ` Michael Smith
2010-06-09 13:53 ` Frans Meulenbroeks
2010-06-09 14:57 ` Chris Larson
2010-06-09 16:53 ` Philip Balister
2010-06-09 17:37 ` Khem Raj
2010-06-11 8:06 ` Frans Meulenbroeks
2010-06-11 18:29 ` Koen Kooi
2010-06-11 21:37 ` Richard Purdie
2010-06-12 7:37 ` Koen Kooi
2010-06-12 11:12 ` Frans Meulenbroeks
2010-06-12 11:47 ` Graeme Gregory
2010-06-12 12:20 ` Frans Meulenbroeks
2010-06-30 10:26 ` Holger Freyther
2010-06-30 11:05 ` Koen Kooi
2010-06-30 13:04 ` Frans Meulenbroeks
2010-06-30 13:19 ` Holger Freyther [this message]
2010-07-01 8:56 ` Koen Kooi
2010-07-01 11:52 ` Frans Meulenbroeks
2010-07-01 12:07 ` Graeme Gregory
2010-07-01 13:43 ` Frans Meulenbroeks
2010-07-01 17:59 ` Mark Brown
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=4C2B446A.5040301@freyther.de \
--to=holger+oe@freyther.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.