From: Trevor Woerner <twoerner@gmail.com>
To: Jeff Osier-Mixon <jefro@jefro.net>
Cc: "openembedded-members@lists.openembedded.org"
<openembedded-members@lists.openembedded.org>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Please help edit OEDAM minutes
Date: Fri, 13 May 2016 09:57:07 -0400 [thread overview]
Message-ID: <20160513135707.GA30983@linux-fl6i> (raw)
In-Reply-To: <CA+YB3rZCfCiLQEg5Br78ZQ=6QJQiXnh_pGTr0-XFQZFkwniYLA@mail.gmail.com>
On Thu 2016-05-12 @ 04:32:01 PM, Jeff Osier-Mixon wrote:
> I admit defeat. I have been "trying to get to" the OEDAM minutes for a
> month and I am clearly not getting to it, so I am now getting out of
> the way. We are crowdsourcing these minutes, because collaborative
> effort is what we do best.
>
> My raw notes from the meeting are here. If you were present, please
> help edit, fill in gaps, etc.
>
> https://docs.google.com/document/d/1rPvy-QQkP0Z4a0PGOBkljfzGGzFVWREDz18vZzWyL9s/edit?usp=sharing
Ok, I'll take a stab at some formatting and stuff.
WARNING: multiple messages have this Message-ID (diff)
From: Trevor Woerner <twoerner@gmail.com>
To: Jeff Osier-Mixon <jefro@jefro.net>
Cc: "openembedded-members@lists.openembedded.org"
<openembedded-members@lists.openembedded.org>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Please help edit OEDAM minutes
Date: Fri, 13 May 2016 09:57:07 -0400 [thread overview]
Message-ID: <20160513135707.GA30983@linux-fl6i> (raw)
In-Reply-To: <CA+YB3rZCfCiLQEg5Br78ZQ=6QJQiXnh_pGTr0-XFQZFkwniYLA@mail.gmail.com>
On Thu 2016-05-12 @ 04:32:01 PM, Jeff Osier-Mixon wrote:
> I admit defeat. I have been "trying to get to" the OEDAM minutes for a
> month and I am clearly not getting to it, so I am now getting out of
> the way. We are crowdsourcing these minutes, because collaborative
> effort is what we do best.
>
> My raw notes from the meeting are here. If you were present, please
> help edit, fill in gaps, etc.
>
> https://docs.google.com/document/d/1rPvy-QQkP0Z4a0PGOBkljfzGGzFVWREDz18vZzWyL9s/edit?usp=sharing
Ok, I'll take a stab at some formatting and stuff.
next prev parent reply other threads:[~2016-05-13 13:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 23:32 Please help edit OEDAM minutes Jeff Osier-Mixon
2016-05-13 13:57 ` Trevor Woerner [this message]
2016-05-13 13:57 ` Trevor Woerner
2016-05-13 17:24 ` [OE-core] " Trevor Woerner
2016-05-13 17:24 ` Trevor Woerner
2016-05-13 17:51 ` [OE-core] " Jeff Osier-Mixon
2016-05-13 17:51 ` Jeff Osier-Mixon
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=20160513135707.GA30983@linux-fl6i \
--to=twoerner@gmail.com \
--cc=jefro@jefro.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-members@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.