From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: "Litzung Chen (陳利琮)" <Litzung.Chen@quantatw.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Quanta's CCLA Schedule A update 2023-03-20
Date: Mon, 20 Mar 2023 15:45:20 -0400 [thread overview]
Message-ID: <f93b92cdf5eb0066d3f1e48fa4d88539c29e5977.camel@fuzziesquirrel.com> (raw)
In-Reply-To: <TY2PR04MB3952B507D338A69F62D05C16F1809@TY2PR04MB3952.apcprd04.prod.outlook.com>
On Mon, 2023-03-20 at 07:19 +0000, Litzung Chen (陳利琮) wrote:
> Hi Brad,
>
> Attached is the updated Schedule A of CCLA from Quanta, please help
> review.
Hi Litzung
You are not listed as a CLA Manager on the most recent Schedule A we
have on file. For both mine and Quantas protection, I can only accept
Schedule A updates from CLA Managers. Can you please have one of the
existing CLA managers send the update? If you would like to make
Schedule A updates after that, have them add "CLA Manager" next to your
name.
> And I wold like to upload the CCLA file to Quanta google driver
> folder.
>
> Could you also help me to apply permission?
I would love to help you with this once you have been added to Schedule
A with "CLA Manager" next to your name. This update needs to be sent by
an existing CLA Manager.
Apologies, I realize this is a hassle - but again this is for both mine
and Quanta's protection.
Thanks,
Brad
next prev parent reply other threads:[~2023-03-20 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 7:19 Quanta's CCLA Schedule A update 2023-03-20 Litzung Chen (陳利琮)
2023-03-20 19:45 ` Brad Bishop [this message]
2023-03-22 9:17 ` 回覆: [External] Re: Quanta's CCLA Schedule A update 2023-03-20Wayland.Lee@quantatw.com <Wayland.Lee@quantatw.com> Richard Tung (董彥屏)
2023-03-24 21:24 ` Brad Bishop
2023-08-21 10:15 ` Quantas CCLA Schedule A update 2023-08-21 Litzung Chen (陳利琮)
2023-11-08 3:14 ` Quantas CCLA Schedule A update 2023-11-08 Litzung Chen (陳利琮)
2023-11-10 15:14 ` Andrew Geissler
2024-03-27 10:19 ` Quantas CCLA Schedule A update 2024-03-27 Litzung Chen (陳利琮)
2024-03-27 17:24 ` 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=f93b92cdf5eb0066d3f1e48fa4d88539c29e5977.camel@fuzziesquirrel.com \
--to=bradleyb@fuzziesquirrel.com \
--cc=Litzung.Chen@quantatw.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 read-only IMAP folder(s) and NNTP newsgroup(s).