public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Feng Xue OS <fxue@os.amperecomputing.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>, Andreas Schwab <schwab@suse.de>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
	"gcc@gcc.gnu.org"	<gcc@gcc.gnu.org>,
	"overseers@sourceware.org" <overseers@sourceware.org>
Subject: Re: How to modify Bugzilla tracker
Date: Fri, 13 Dec 2019 02:13:00 -0000	[thread overview]
Message-ID: <BYAPR01MB4869D628911425EA61C38EC4F7540@BYAPR01MB4869.prod.exchangelabs.com> (raw)
In-Reply-To: <CAH6eHdTrxTGzGO=nx+Ce5b3djXzJkQ+rwRw75T96eTePAPUZ0Q@mail.gmail.com>

> On Thu, 12 Dec 2019 at 09:29, Andreas Schwab <schwab@suse.de> wrote:
>>
>> On Dez 12 2019, Jonathan Wakely wrote:
>>
>> > On Thu, 12 Dec 2019 at 09:19, Thomas Schwinge wrote:
>> >>
>> >> Hi!
>> >>
>> >> I'm not an admin there; CCing the Overseers.
>> >>
>> >> On 2019-12-12T01:58:46+0000, Feng Xue OS <fxue@os.amperecomputing.com> wrote:
>> >> > I have a sourceware.org account, but can not correlate the account with Bugzilla login.
>> >>
>> >> Yes: 'gcc.gnu.org' is a separate Bugzilla instance.
>> >>
>> >> > Just want to assign a tracker to someone.
>> >>
>> >> To be able to do that, as far as I know, you'll need to use (set up a
>> >> new?) account associated with your 'fxue@gcc.gnu.org' email address.
>> >> Addresses '@gcc.gnu.org' automatically get special permissions.
>> >>
>> >> I see you do have an account 'fxue@os.amperecomputing.com'.  Maybe it's
>> >> possible to add another email address to that one (or replace it?), or if
>> >> not, I remember that I once (manually?) got two accounts merged into
>> >> 'tschwinge@gcc.gnu.org', so that's another option for you, assuming you'd
>> >> like just one account.
>> >
>> > @sourceware.org and @gcc.gnu.org accounts are also separate, and I
>> > don't see your name in the GCC MAINTAINERS file (apologies if I missed
>> > it).
>>
>> The fxue@gcc.gnu.org account already exists, he just needs to use it.

> Ah OK, so just use the "reset password" link to get access to that account then.

But I did not know I own fxue@gcc.gnu.org, and do not know how to access
the email, to which "reset password" instructions will be sent. 

Actually, I tried to ask for oversees to create a gcc.gnu.org account, but was told 
it is not needed for I already have one @sourceware.org.

BTW: I'm not a maintainer.

Thanks,
Feng

  reply	other threads:[~2019-12-13  2:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BYAPR01MB4869504569EB57BC007D02CDF75A0@BYAPR01MB4869.prod.exchangelabs.com>
     [not found] ` <CAH6eHdTFWrPMSUvq2raWi=rxmdBEb-ssnxLgpfsEF8k0tNfx_g@mail.gmail.com>
     [not found]   ` <BYAPR01MB486902A66F9EAE1D2113409FF7550@BYAPR01MB4869.prod.exchangelabs.com>
2019-12-12  9:19     ` Thomas Schwinge
2019-12-12  9:21       ` Jonathan Wakely
2019-12-12  9:29         ` Andreas Schwab
2019-12-12  9:43           ` Jonathan Wakely
2019-12-13  2:13             ` Feng Xue OS [this message]
2019-12-13  3:05               ` Feng Xue OS

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=BYAPR01MB4869D628911425EA61C38EC4F7540@BYAPR01MB4869.prod.exchangelabs.com \
    --to=fxue@os.amperecomputing.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=overseers@sourceware.org \
    --cc=schwab@suse.de \
    --cc=thomas@codesourcery.com \
    /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).