From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: tsc <tsc@lists.openembedded.org>
Subject: Re: [oe] Minutes: OE-TSC Meeting 22-Nov-2011
Date: Thu, 15 Dec 2011 13:04:58 +0000 [thread overview]
Message-ID: <1323954298.4568.22.camel@ted> (raw)
In-Reply-To: <1323952431.24417.207.camel@phil-desktop>
On Thu, 2011-12-15 at 12:33 +0000, Phil Blundell wrote:
> On Fri, 2011-11-25 at 13:38 -0800, Jeff Osier-Mixon wrote:
> > next meeting scheduled 6-Dec-2011
>
> Were there any minutes posted for this meeting? I don't recall having
> seen them.
The meeting on the 6th didn't happen as we all got confused about the
meeting time changes. We did have a meeting on the 13th which I believe
Jeff should have minutes for shortly.
Cheers,
Richard
next prev parent reply other threads:[~2011-12-15 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 21:38 Minutes: OE-TSC Meeting 22-Nov-2011 Jeff Osier-Mixon
2011-12-15 12:33 ` [oe] " Phil Blundell
2011-12-15 13:04 ` Richard Purdie [this message]
2011-12-15 15:52 ` 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=1323954298.4568.22.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=tsc@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