From: krtaylor <kurt.r.taylor@gmail.com>
To: Duke KH Du <dukh@lenovo.com>, Benjamin Fair <benjaminfair@google.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: [External] Re: Add member into Lenovo designated employees list
Date: Tue, 14 Jan 2020 10:12:54 -0600 [thread overview]
Message-ID: <ce1d6193-be75-7509-3abd-efdb9d743ae7@gmail.com> (raw)
In-Reply-To: <9f04dca2a58d4fb283c80e346a3b05fa@lenovo.com>
On 1/13/20 5:56 PM, Duke KH Du wrote:
> Hi Kurt,
>
> I had updated the information you needed on 12/17 already.
> Refer to the attached mail.
You are updated and good to go! Thanks for keeping this list current.
My apologies, for whatever reason I did not receive that on the 17th. I
appreciate your patience, but always feel free to ping me on IRC if you
haven't heard anything from me in a couple of days.
Kurt Taylor (krtaylor)
> Thanks.
>
> -----Original Message-----
> From: krtaylor <kurt.r.taylor@gmail.com>
> Sent: Monday, January 13, 2020 3:55 PM
> To: Benjamin Fair <benjaminfair@google.com>
> Cc: openbmc@lists.ozlabs.org; Duke KH Du <dukh@lenovo.com>
> Subject: [External] Re: Add member into Lenovo designated employees list
>
> On 1/10/20 11:22 AM, Benjamin Fair wrote:
>> Hi Kurt,
>>
>> Could you take a look at the CCLA update from Lenovo when you get a chance?
>
> Yes, I have already communicated with them (Dec 13th) about what I am needing.
>
> Kurt Taylor (krtaylor)
>
>>
>> Thanks,
>> Benjamin
>>
>>
>> On Fri, 6 Dec 2019 at 12:45, Duke KH Du <dukh@lenovo.com
>> <mailto:dukh@lenovo.com>> wrote:
>>
>> Hi Master,____
>>
>> __ __
>>
>> I would like to add more members of Lenovo in the designated
>> employee list as below in Red.____
>>
>> Could you help on that?____
>>
>> __ __
>>
>> Schedule A____
>>
>> Initial list of designated employees. NB: authorization is not tied
>> to particular Contributions.____
>>
>> Please indicate “CLA Manager”next to the name of any employees
>> listed below that are____
>>
>> authorized to add or remove designated employees from this list in
>> the future.____
>>
>> __ __
>>
>> CLA Manager:____
>>
>> Duke Du dukh@lenovo.com <mailto:dukh@lenovo.com>____
>>
>> __ __
>>
>> Other designated employees:____
>>
>> Andrew Peng pengms1@lenovo.com <mailto:pengms1@lenovo.com>____
>>
>> Yonghui Liu liuyh21@lenovo.com <mailto:liuyh21@lenovo.com>____
>>
>> Lisa Liu liuyj19@lenovo.com <mailto:liuyj19@lenovo.com>____
>>
>> __ __
>>
>> Payne Yang pyang4@lenovo.com <mailto:pyang4@lenovo.com>____
>>
>> Harry Sung hsung1@lenovo.com <mailto:hsung1@lenovo.com>____
>>
>> Ivan Li rli11@lenovo.com <mailto:rli11@lenovo.com>____
>>
>> Derek Lin dlin23@lenovo.com <mailto:dlin23@lenovo.com>____
>>
>> __ __
>>
>> Thanks.____
>>
>> *From:* Duke KH Du
>> *Sent:* Monday, April 8, 2019 8:44 PM
>> *To:* openbmc@lists.ozlabs.org <mailto:openbmc@lists.ozlabs.org>
>> *Subject:* Add member into Lenovo designated employees list____
>>
>> __ __
>>
>> Hi master,____
>>
>> __ __
>>
>> I would like to add our new member in Lenovo designated employees
>> list as below in RED color.____
>>
>> __ __
>>
>> Could you help on it?____
>>
>> Thanks.____
>>
>> __ __
>>
>> Schedule A____
>>
>> Initial list of designated employees. NB: authorization is not tied
>> to particular Contributions.____
>>
>> Please indicate “CLA Manager”next to the name of any employees
>> listed below that are____
>>
>> authorized to add or remove designated employees from this list in
>> the future.____
>>
>> __ __
>>
>> CLA Manager:____
>>
>> Duke Du dukh@lenovo.com <mailto:dukh@lenovo.com>____
>>
>> __ __
>>
>> Other designated employees:____
>>
>> Andrew Peng pengms1@lenovo.com <mailto:pengms1@lenovo.com>____
>>
>> __ __
>>
>> Yonghui Liu liuyh21@lenovo.com <mailto:liuyh21@lenovo.com>____
>>
>> __ __
>>
>> Lisa Liu liuyj19@lenovo.com <mailto:liuyj19@lenovo.com>____
>>
>> __ __
>>
>
next prev parent reply other threads:[~2020-01-14 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 20:44 Add member into Lenovo designated employees list Duke KH Du
2019-12-10 2:54 ` Benjamin Fair
2020-01-10 17:22 ` Benjamin Fair
2020-01-13 23:54 ` krtaylor
2020-01-13 23:56 ` [External] " Duke KH Du
2020-01-14 16:12 ` krtaylor [this message]
2021-03-31 7:14 Duke KH Du
2021-03-31 13:18 ` Andrew Geissler
2021-11-09 7:52 ` [External] " Duke KH Du
2021-11-09 17:02 ` Andrew Geissler
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=ce1d6193-be75-7509-3abd-efdb9d743ae7@gmail.com \
--to=kurt.r.taylor@gmail.com \
--cc=benjaminfair@google.com \
--cc=dukh@lenovo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).