From: "James Mihm (via Google Drive)" <james.mihm@gmail.com>
To: openbmc@lists.ozlabs.org
Subject: OpenBMC Hackathon
Date: Wed, 10 Oct 2018 16:00:26 +0000 [thread overview]
Message-ID: <000000000000e6ad030577e1f323@google.com> (raw)
In-Reply-To: 64c3fec3-584c-4373-b9ad-dfb235a6d2de@docs-share.google.com
[-- Attachment #1: Type: text/plain, Size: 302 bytes --]
I've shared an item with you:
OpenBMC Hackathon
https://drive.google.com/drive/folders/1aF0cy9_jwJrFvytv2jp1pI3Rf-uXHACI?usp=sharing&ts=5bbe221a
It's not an attachment -- it's stored online. To open this item, just click
the link above.
Here's a link to where the OpenBMC Hackathon presentations.
[-- Attachment #2: Type: text/html, Size: 6118 bytes --]
next parent reply other threads:[~2018-10-10 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <64c3fec3-584c-4373-b9ad-dfb235a6d2de@docs-share.google.com>
2018-10-10 16:00 ` James Mihm (via Google Drive) [this message]
2018-06-19 0:00 OpenBMC Hackathon 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=000000000000e6ad030577e1f323@google.com \
--to=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.