From: Luke Chen <luke_chen@aspeedtech.com>
To: James Mihm <james.mihm@gmail.com>, "andrew@aj.id.au" <andrew@aj.id.au>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: RE: Poll - Fall 2018 OpenBMC Hackathon
Date: Tue, 19 Jun 2018 06:08:52 +0000 [thread overview]
Message-ID: <c7333926d7df413ba2bb8c21e3987552@TWMBX02.aspeed.com> (raw)
In-Reply-To: <CADy_Pt2rWNu7NuTfQWfP5T+mzfVW3FCbc_8j_Ss+zOwiy68sRA@mail.gmail.com>
Dear James
Thank you for sending me the email, I already filled out the form.
And I also subscribed on OpenBMC for the mailing list just now.
Best wishes
Luke Chen
(O) : +886-3-5789568
(M) : +886-935-592-892
-----Original Message-----
From: openbmc <openbmc-bounces+luke_chen=aspeedtech.com@lists.ozlabs.org> On Behalf Of James Mihm
Sent: Tuesday, June 19, 2018 1:57 PM
To: andrew@aj.id.au
Cc: openbmc@lists.ozlabs.org
Subject: Re: Poll - Fall 2018 OpenBMC Hackathon
Andrew, Great idea...just added either and neither.
James.
On Mon, Jun 18, 2018 at 10:02 PM Andrew Jeffery <andrew@aj.id.au> wrote:
>
> On Tue, 19 Jun 2018, at 09:26, james.mihm@gmail.com wrote:
> > I've invited you to fill out the following form:
> > OpenBMC Hackathon
> >
> > To fill it out, visit:
> > https://docs.google.com/forms/d/e/1FAIpQLSeGn5x4Y-6vgu3_AyY3YsIr_JVU5YCjLXufuXxdT9Qy6sz42Q/viewform?c=0&w=1&usp=mail_form_link
> >
> > I've invited you to fill out a form:
> >
> > Google Forms: Create and analyze surveys.
>
> Maybe we should add 'either' and 'neither' options so people can register their interest appropriately?
>
> Cheers,
>
> Andrew
next prev parent reply other threads:[~2018-06-19 6:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 23:56 Poll - Fall 2018 OpenBMC Hackathon james.mihm
2018-06-19 5:01 ` Andrew Jeffery
2018-06-19 5:57 ` James Mihm
2018-06-19 6:08 ` Luke Chen [this message]
2018-06-19 6:09 ` James Mihm
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=c7333926d7df413ba2bb8c21e3987552@TWMBX02.aspeed.com \
--to=luke_chen@aspeedtech.com \
--cc=andrew@aj.id.au \
--cc=james.mihm@gmail.com \
--cc=openbmc@lists.ozlabs.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.