From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-members@lists.openembedded.org
Cc: openembedded-core <openembedded-core@lists.openembedded.org>,
Yocto Project <yocto@yoctoproject.org>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
Anders Darander <anders@chargestorm.se>
Subject: Re: [yocto] OpenEmbedded eV General Assembly
Date: Thu, 08 Nov 2012 07:35:12 +0100 [thread overview]
Message-ID: <1352356512.9083.2.camel@ted> (raw)
In-Reply-To: <CA+YB3rY9SgvESvhZk-qYzZ=QJqz-n8xJA_zrHcrwwKcoLAnd2w@mail.gmail.com>
On Wed, 2012-11-07 at 19:21 -0800, Jeff Osier-Mixon wrote:
> So how did it go? Were notes taken?
>
Everything went fine and it didn't take that long, unlike some of the
previous meetings. Notes are at the end of:
http://www.openembedded.org/wiki/Barcelona,_2012
Cheers,
Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-members@lists.openembedded.org
Cc: openembedded-core <openembedded-core@lists.openembedded.org>,
Yocto Project <yocto@yoctoproject.org>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
Anders Darander <anders@chargestorm.se>
Subject: Re: [yocto] [OE-core] OpenEmbedded eV General Assembly
Date: Thu, 08 Nov 2012 07:35:12 +0100 [thread overview]
Message-ID: <1352356512.9083.2.camel@ted> (raw)
In-Reply-To: <CA+YB3rY9SgvESvhZk-qYzZ=QJqz-n8xJA_zrHcrwwKcoLAnd2w@mail.gmail.com>
On Wed, 2012-11-07 at 19:21 -0800, Jeff Osier-Mixon wrote:
> So how did it go? Were notes taken?
>
Everything went fine and it didn't take that long, unlike some of the
previous meetings. Notes are at the end of:
http://www.openembedded.org/wiki/Barcelona,_2012
Cheers,
Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-members@lists.openembedded.org
Cc: openembedded-core <openembedded-core@lists.openembedded.org>,
Yocto Project <yocto@yoctoproject.org>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: [OE-core] OpenEmbedded eV General Assembly
Date: Thu, 08 Nov 2012 07:35:12 +0100 [thread overview]
Message-ID: <1352356512.9083.2.camel@ted> (raw)
In-Reply-To: <CA+YB3rY9SgvESvhZk-qYzZ=QJqz-n8xJA_zrHcrwwKcoLAnd2w@mail.gmail.com>
On Wed, 2012-11-07 at 19:21 -0800, Jeff Osier-Mixon wrote:
> So how did it go? Were notes taken?
>
Everything went fine and it didn't take that long, unlike some of the
previous meetings. Notes are at the end of:
http://www.openembedded.org/wiki/Barcelona,_2012
Cheers,
Richard
next prev parent reply other threads:[~2012-11-08 6:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 13:04 OpenEmbedded eV General Assembly Anders Darander
2012-11-07 13:04 ` [OE-core] " Anders Darander
2012-11-07 13:17 ` Philip Balister
2012-11-07 13:17 ` [OE-core] " Philip Balister
2012-11-08 3:21 ` [yocto] " Jeff Osier-Mixon
2012-11-08 3:21 ` [OE-core] " Jeff Osier-Mixon
2012-11-08 3:21 ` [yocto] " Jeff Osier-Mixon
2012-11-08 6:35 ` Richard Purdie [this message]
2012-11-08 6:35 ` Richard Purdie
2012-11-08 6:35 ` [yocto] " Richard Purdie
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=1352356512.9083.2.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=anders@chargestorm.se \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-members@lists.openembedded.org \
--cc=yocto@yoctoproject.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.