From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [TSC] First Meeting
Date: Sun, 10 Jan 2010 16:57:10 +0100 [thread overview]
Message-ID: <hictcm$b0c$1@ger.gmane.org> (raw)
In-Reply-To: <ac9c93b11001070004j6d2c599bie9249c7aab3758ad@mail.gmail.com>
Frans Meulenbroeks wrote:
> May I suggest that the TSC thinks of a mechanism for developers to
> bring topics to the TSC table (something somewhat more structured than
> just mailing one of the TSC members or mailing it to the list
How about the bug tracker? I could add a specific category and cc TSC
members when tasks are added.
next prev parent reply other threads:[~2010-01-10 15:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 14:00 [TSC] First Meeting Graeme Gregory
2009-12-22 15:47 ` Frans Meulenbroeks
2009-12-22 16:13 ` Graeme Gregory
2009-12-22 16:43 ` Koen Kooi
2009-12-22 16:48 ` Philip Balister
2009-12-23 19:24 ` Richard Purdie
2009-12-23 23:35 ` Richard Purdie
2009-12-29 15:52 ` Graeme Gregory
2009-12-29 18:43 ` Koen Kooi
2009-12-29 20:30 ` Richard Purdie
2009-12-30 8:47 ` Koen Kooi
2009-12-30 14:45 ` Graeme Gregory
2009-12-31 10:16 ` Frans Meulenbroeks
2009-12-31 10:29 ` Phil Blundell
2010-01-04 10:46 ` Richard Purdie
2010-01-04 10:53 ` Koen Kooi
2010-01-04 11:24 ` Michael 'Mickey' Lauer
2010-01-04 11:46 ` Richard Purdie
2010-01-04 10:57 ` Frans Meulenbroeks
2010-01-04 11:02 ` Graeme Gregory
2010-01-04 11:52 ` Richard Purdie
2010-01-04 15:27 ` Chris Larson
2010-01-04 18:19 ` Michael 'Mickey' Lauer
2010-01-05 11:11 ` Graeme Gregory
2010-01-05 14:43 ` Richard Purdie
2010-01-05 16:26 ` Chris Larson
2010-01-07 8:04 ` Frans Meulenbroeks
2010-01-07 9:18 ` Graeme Gregory
2010-01-10 15:57 ` Rolf Leggewie [this message]
2010-01-10 16:16 ` Richard Purdie
2010-01-04 19:06 ` Denys Dmytriyenko
2010-01-04 19:17 ` Phil Blundell
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='hictcm$b0c$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.