From: Paul Koning <paul_koning@dell.com>
To: Andrew Pinski <pinskia@gcc.gnu.org>
Cc: overseers@gcc.gnu.org
Subject: Re: GCC Bugzilla
Date: Fri, 29 Oct 2010 00:31:00 -0000 [thread overview]
Message-ID: <B8FE5D8B-5386-4197-8931-8FBD05137A40@dell.com> (raw)
In-Reply-To: <AANLkTikfZVWTkFse8jtVhYjHq36=ZsD71GgR+YnHfauk@mail.gmail.com>
Thanks, I'm all set now.
paul
On Oct 28, 2010, at 5:38 PM, Andrew Pinski wrote:
> You should be able to use your @gcc.gnu.org account to do everything
> on the GCC bugzilla. That account has the correct privileges.
>
> The easiest way to do this is do "forgot passport" and use your @gcc
> email address. This will sent the information to where your
> @gcc.gnu.org is forwarded to.
> if you need to change the forwarding address use:
> ssh account@gcc.gnu.org email newemailaddress
>
> Thanks,
> Andrew Pinski
next prev parent reply other threads:[~2010-10-29 0:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 21:31 Paul Koning
2010-10-28 21:38 ` Andrew Pinski
2010-10-29 0:31 ` Paul Koning [this message]
2016-10-07 15:37 GCC bugzilla nicolas bouillot
2017-03-12 9:46 joris
2017-03-30 10:20 GCC Bugzilla Alfred Agrell
2023-11-30 5:14 gcc bugzilla Joern Rennecke
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=B8FE5D8B-5386-4197-8931-8FBD05137A40@dell.com \
--to=paul_koning@dell.com \
--cc=overseers@gcc.gnu.org \
--cc=pinskia@gcc.gnu.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).