public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Cui, Lili" <lili.cui@intel.com>,
	Overseers mailing list <overseers@sourceware.org>
Cc: "cuilili8868@gmail.com" <cuilili8868@gmail.com>,
	"Liu, Hongtao" <hongtao.liu@intel.com>
Subject: Re: Request from Lili Cui
Date: Mon, 27 Jun 2022 17:06:25 +0200	[thread overview]
Message-ID: <d524bdffd53cec8f1d3c9c63c865d989f3d0e054.camel@klomp.org> (raw)
In-Reply-To: <SJ0PR11MB5600A0499DE6433952E0E8F49EB99@SJ0PR11MB5600.namprd11.prod.outlook.com>

Hi Lili,

On Mon, 2022-06-27 at 13:24 +0000, Cui, Lili wrote:
> > On Mon, 2022-06-27 at 07:39 +0000, cuilili8868--- via Overseers
> > wrote:
> > > Lili Cui is requesting an account:
> > > 
> > > Login: lilicui
> > > Email: cuilili8868@gmail.com
> > > Project: gcc
> > > Approver: hongtao.liu@intel.com
> > 
> > Just to confirm, you are communicating with the GCC community on
> > the
> > mailinglists as lili.cui@intel.com but want your account to be
> > linked to
> > cuilili8868@gmail.com ?
> > 
> 
> Yes, I want to use cuilili8868@gmail.com as my account, do I need to
> make any changes?

Thanks for confirming from your other email address.
Since you already have an account (cuilili) for binutils I will add
that account to the gcc group. If you want to update your forwarding
address you can follow these instructions:
https://sourceware.org/sourceware/accountinfo.html

Cheers,

Mark

  reply	other threads:[~2022-06-27 15:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27  7:39 cuilili8868
2022-06-27 13:13 ` Mark Wielaard
2022-06-27 13:24   ` Cui, Lili
2022-06-27 15:06     ` Mark Wielaard [this message]
2022-06-28  0:12       ` Cui, Lili
  -- strict thread matches above, loose matches on Subject: below --
2022-06-15  1:36 cuilili8868
2022-06-15 15:13 ` Christopher Faylor
2020-04-02  8:21 lili.cui
2020-04-02 14:19 ` Lu, Hongjiu

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=d524bdffd53cec8f1d3c9c63c865d989f3d0e054.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=cuilili8868@gmail.com \
    --cc=hongtao.liu@intel.com \
    --cc=lili.cui@intel.com \
    --cc=overseers@sourceware.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).