From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: Ed Tanous <edtanous@google.com>
Cc: Willy Tu <wltu@google.com>,
vernon.mauery@linux.intel.com,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
chunhui.jia@linux.intel.com, apparao.puli@linux.intel.com,
Vijay Khemka <vijaykhemka@fb.com>
Subject: Re: Intel-ipmi-oem repo
Date: Thu, 14 Jan 2021 13:53:16 -0500 [thread overview]
Message-ID: <20210114185316.vmlaa7nn7vlxq2wh@thinkpad.fuzziesquirrel.com> (raw)
In-Reply-To: <CAH2-KxBgmEmfeQxsbTa1RPVO_nm5=G+ayZ9aDM+1hf7oRtoDGA@mail.gmail.com>
On Thu, Jan 14, 2021 at 08:38:41AM -0800, Ed Tanous wrote:
>I only suggested a new repo originally because today it's a separate repo,
>and the long ago patch to add it directly to ipmid got the feedback that
>was too different than the existing to go there.
Hrm...this is not at all how I remember it. I thought the feedback IBM
tried to give back then was "please don't break the code that is already
there." I apologize if what came through was "your code is too
different, no thanks" ...that was definitely never the intent.
-brad
next prev parent reply other threads:[~2021-01-14 19:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 2:54 Intel-ipmi-oem repo Willy Tu
2021-01-14 14:39 ` Brad Bishop
2021-01-14 16:38 ` Ed Tanous
2021-01-14 17:38 ` Vernon Mauery
2021-01-14 19:40 ` Brad Bishop
2021-01-14 20:06 ` Ed Tanous
2021-01-14 21:46 ` Willy Tu
2021-01-15 2:23 ` Lei Yu
2021-01-15 4:20 ` chunhui.jia
2021-01-15 5:59 ` Lei Yu
2021-01-14 18:53 ` Brad Bishop [this message]
2021-01-14 20:00 ` Ed Tanous
-- strict thread matches above, loose matches on Subject: below --
2019-01-22 18:16 Vijay Khemka
2019-01-22 20:53 ` Brad Bishop
2019-01-22 21:02 ` Patrick Venture
2019-01-22 21:31 ` Vijay Khemka
2019-01-22 22:05 ` Ed Tanous
2019-01-22 22:22 ` Vijay Khemka
2019-01-22 23:25 ` Ed Tanous
2019-01-22 23:58 ` Vijay Khemka
2019-01-24 0:42 ` Bills, Jason M
2019-01-23 6:13 ` Tom Joseph
2019-01-23 16:34 ` Ed Tanous
2019-01-23 16:59 ` Brad Bishop
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=20210114185316.vmlaa7nn7vlxq2wh@thinkpad.fuzziesquirrel.com \
--to=bradleyb@fuzziesquirrel.com \
--cc=apparao.puli@linux.intel.com \
--cc=chunhui.jia@linux.intel.com \
--cc=edtanous@google.com \
--cc=openbmc@lists.ozlabs.org \
--cc=vernon.mauery@linux.intel.com \
--cc=vijaykhemka@fb.com \
--cc=wltu@google.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.