All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: Rick Altherr <raltherr@google.com>
Cc: openbmc@lists.ozlabs.org, Martin Roth <gaumless@gmail.com>,
	Timothy Pearson <tpearson@raptorengineeringinc.com>
Subject: Re: OT: Crowdfunding to port OpenBMC to Asus KGPE-D16
Date: Tue, 28 Feb 2017 09:49:19 +0100	[thread overview]
Message-ID: <1488271759.4286.43.camel@users.sourceforge.net> (raw)
In-Reply-To: <CAPLgG=k8neY9VbJW624zvQO1SzXWPjza+xbUHnhWo4V94QuQmg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 721 bytes --]

Dear Rick,


Am Montag, den 27.02.2017, 13:01 -0800 schrieb Rick Altherr:
> I replied to Raptor's tweet asking why they preferred Facebook's OpenBMC
> over the IBM one. I find it odd that you are asking developers on the
> latter to fund development for the former.

I am sorry about that. It was solely my ignorance. I just search for
*OpenBMC* and *mailing list*, and used that list address. I didn’t know
that there is a Facebook OpenBMC and an IBM one, as I had just read
about Facebook’s OpenBMC a few years ago in the press, and nothing
else.

Now I am smarter, and hope that will get IBM’s OpenBMC funded and
running on that device/board too.

So please spread the word.


Thanks,

Paul

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      parent reply	other threads:[~2017-02-28  8:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-26 18:49 OT: Crowdfunding to port OpenBMC to Asus KGPE-D16 Paul Menzel
2017-02-27 21:01 ` Rick Altherr
2017-02-27 21:15   ` Timothy Pearson
2017-02-27 21:24     ` Rick Altherr
2017-02-27 21:32       ` Timothy Pearson
2017-02-28  8:49   ` Paul Menzel [this message]

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=1488271759.4286.43.camel@users.sourceforge.net \
    --to=paulepanter@users.sourceforge.net \
    --cc=gaumless@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=raltherr@google.com \
    --cc=tpearson@raptorengineeringinc.com \
    /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.