From: Mark Wielaard <mark@klomp.org>
To: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
Cc: Overseers mailing list <overseers@sourceware.org>,
hubicka@kam.mff.cuni.cz, nitinkumar4268@gmail.com,
hubicka@ucw.cz
Subject: Re: Request from Nitin Kumar
Date: Wed, 29 Jun 2022 17:58:35 +0200 [thread overview]
Message-ID: <0ee884cf5ca765713d0079e01ce04b2583d20e0d.camel@klomp.org> (raw)
In-Reply-To: <20220629151521.cbi45ri2wbiwrqet@cgf.cx>
Hi,
On Wed, 2022-06-29 at 11:15 -0400, Christopher Faylor wrote:
> On Wed, Jun 29, 2022 at 03:47:54PM +0200, Mark Wielaard wrote:
> > On Tue, 2022-06-28 at 08:41 +0000, nitinkumar4268--- via Overseers
> > wrote:
> > > Nitin Kumar is requesting an account:
> >
> > Sorry, I cannot find you on the gcc/gcc-patches mailinglists as
> > contributor, also that email address for Jan Hubička on file as gcc
> > maintainer.
>
> I think you mean that's NOT the email address on file for Jan
> Hubička.
Yes, I meant NOT, sorry.
> I've Cc'ed the email address from the gcc MAINTAINERS file.
>
> > If you have been communicating under a different email address
> > could
> > you file for an account using that address and use Jan's maintainer
> > address for confirmation?
>
> Is participation in the gcc/binutils/whatever mailing list a new
> requirement for an account?
It was me being paranoid since none of the email addresses lined up.
Then I do a quick check that the person requesting an account is
actually an active community member.
Cheers,
Mark
prev parent reply other threads:[~2022-06-29 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 8:41 nitinkumar4268
2022-06-29 13:47 ` Mark Wielaard
2022-06-29 15:15 ` Christopher Faylor
2022-06-29 15:48 ` Jan Hubicka
2022-06-29 15:58 ` Christopher Faylor
2022-06-29 15:58 ` Mark Wielaard [this message]
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=0ee884cf5ca765713d0079e01ce04b2583d20e0d.camel@klomp.org \
--to=mark@klomp.org \
--cc=cgf-use-the-mailinglist-please@sourceware.org \
--cc=hubicka@kam.mff.cuni.cz \
--cc=hubicka@ucw.cz \
--cc=nitinkumar4268@gmail.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).