From: Thomas Schwinge <thomas@codesourcery.com>
To: Feng Xue OS <fxue@os.amperecomputing.com>
Cc: <gcc@gcc.gnu.org>, <overseers@sourceware.org>,
Jonathan Wakely <jwakely.gcc@gmail.com>
Subject: Re: How to modify Bugzilla tracker
Date: Thu, 12 Dec 2019 09:19:00 -0000 [thread overview]
Message-ID: <87zhfx52bn.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <BYAPR01MB486902A66F9EAE1D2113409FF7550@BYAPR01MB4869.prod.exchangelabs.com>
[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]
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.
Grüße
Thomas
> From: Jonathan Wakely <jwakely.gcc@gmail.com>
> Sent: Wednesday, December 11, 2019 7:07 PM
> To: Feng Xue OS
> Cc: gcc@gcc.gnu.org
> Subject: Re: How to modify Bugzilla tracker
>
> On Wed, 11 Dec 2019 at 02:25, Feng Xue OS <fxue@os.amperecomputing.com> wrote:
>>
>> Hi,
>>
>> I want to alter some information of an existing Bugzilla tracker, such as assignee, but found there is no entrance in page of the Bugzilla tracker to do this. How can I get it?
>
> Usually that's restricted to GCC developers, using their user@gcc.gnu.org login.
>
> What do you want to change?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]
next parent reply other threads:[~2019-12-12 9:19 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 [this message]
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
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=87zhfx52bn.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=fxue@os.amperecomputing.com \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@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).