From: Andrew Geissler <geissonator@gmail.com>
To: Duke KH Du <dukh@lenovo.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Add member into Lenovo designated employees list
Date: Wed, 31 Mar 2021 08:18:56 -0500 [thread overview]
Message-ID: <9D88EA1B-4409-4BD8-A341-EAAC8FF0007A@gmail.com> (raw)
In-Reply-To: <SL2PR03MB41392EC887269BEBAF453E96B67C9@SL2PR03MB4139.apcprd03.prod.outlook.com>
> On Mar 31, 2021, at 2:14 AM, Duke KH Du <dukh@lenovo.com> wrote:
>
> Hi Master,
>
> I would like to add our new member in Lenovo designated employees list as below？
> Could you help on it?
Hey Duke, I noticed Lenovo was not added to the script used by jenkins to
validate groups so I put up a commit here for that:
https://gerrit.openbmc-project.xyz/c/openbmc/openbmc-build-scripts/+/41738
Currently the Lenovo gerrit group only has one person in it:
https://gerrit.openbmc-project.xyz/admin/groups/b009effba2bf2e62802e74d749db360d52c2a245,members
And no one is approved to add people currently:
https://gerrit.openbmc-project.xyz/admin/groups/9f33fac15a90496c21b873f5f9918af1a633a47b,members
Could you recommend someone with a gerrit account that we can add to be in
charge of adding new developers from your company to this group?
It does look like ritzenyang needs to be added to the Lenovo CLA though before
he can contribute code?
> Thanks.
>
> ritzenyang ryang14@lenovo.com
next prev parent reply other threads:[~2021-03-31 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 7:14 Add member into Lenovo designated employees list Duke KH Du
2021-03-31 13:18 ` Andrew Geissler [this message]
2021-11-09 7:52 ` [External] " Duke KH Du
2021-11-09 17:02 ` Andrew Geissler
-- strict thread matches above, loose matches on Subject: below --
2019-12-06 20:44 Duke KH Du
2019-12-10 2:54 ` Benjamin Fair
2020-01-10 17:22 ` Benjamin Fair
2020-01-13 23:54 ` krtaylor
2019-04-09 3:43 Duke KH Du
2019-04-15 19:14 ` Kurt Taylor
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=9D88EA1B-4409-4BD8-A341-EAAC8FF0007A@gmail.com \
--to=geissonator@gmail.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 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.