From: Patrick Williams <patrick@stwcx.xyz>
To: "Garrett, Mike (HPE Server Firmware)" <mike.garrett@hpe.com>
Cc: Patrick Williams <patrick@stwcx.xyz>,
"Chang, Abner (HPS SW/FW Technologist)" <abner.chang@hpe.com>,
Deepak Kodihalli <dkodihal@linux.vnet.ibm.com>,
"suryakanth.sekar@linux.intel.com"
<suryakanth.sekar@linux.intel.com>,
Brad Bishop <bradleyb@fuzziesquirrel.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Fix content rendering issue on RemoteBiosConfiguration doc
Date: Mon, 27 Jul 2020 09:56:48 -0500 [thread overview]
Message-ID: <20200727145648.GP3922@heinlein> (raw)
In-Reply-To: <AT5PR8401MB06262BBAB1DDDAE7B9BE80498F720@AT5PR8401MB0626.NAMPRD84.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
On Mon, Jul 27, 2020 at 02:41:52PM +0000, Garrett, Mike (HPE Server Firmware) wrote:
> Thanks Patrick,
>
> The CCLA shows the "initial list" of contributors on Schedule A. What is the mechanism for editing that list and adding names?
>
Hi Mike,
What appears to be past practice is to have either you or Scott send
just an updated copy of your "Schedule A" to the mailing list. Brad or
Kurt will then process it by adding it to the Google Drive.
1. https://lists.ozlabs.org/pipermail/openbmc/2019-November/019495.html
2. https://lists.ozlabs.org/pipermail/openbmc/2019-November/019487.html
3. https://lists.ozlabs.org/pipermail/openbmc/2019-December/019885.html
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-27 14:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-25 3:48 Fix content rendering issue on RemoteBiosConfiguration doc Chang, Abner (HPS SW/FW Technologist)
2020-07-26 7:41 ` Deepak Kodihalli
2020-07-26 7:55 ` Chang, Abner (HPS SW/FW Technologist)
2020-07-27 14:22 ` Patrick Williams
2020-07-27 14:28 ` Chang, Abner (HPS SW/FW Technologist)
2020-07-27 14:41 ` Garrett, Mike (HPE Server Firmware)
2020-07-27 14:56 ` Patrick Williams [this message]
2020-07-27 14:23 ` Patrick Williams
2020-07-27 14:44 ` Deepak Kodihalli
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=20200727145648.GP3922@heinlein \
--to=patrick@stwcx.xyz \
--cc=abner.chang@hpe.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=dkodihal@linux.vnet.ibm.com \
--cc=mike.garrett@hpe.com \
--cc=openbmc@lists.ozlabs.org \
--cc=suryakanth.sekar@linux.intel.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.