From: Yao Qi <yao@codesourcery.com>
To: overseers@sourceware.org
Subject: Re: bugzilla email issues
Date: Fri, 27 May 2011 03:34:00 -0000 [thread overview]
Message-ID: <4DDF1B98.7010002@codesourcery.com> (raw)
In-Reply-To: <4DDEBE79.4010406@codesourcery.com>
On 05/27/2011 04:56 AM, Nathan Froyd wrote:
> 2) I recently attempted to change the email address that froydnj@gcc.gnu.org
> redirects to; unfortunately, I didn't see http://gcc.gnu.org/svnwrite.html and
> tried changing my email under User Preferences/Name and Password in bugzilla.
Nathan,
Run:
ssh froydnj@gcc.gnu.org email YOUR.EMAL@XXX
--
Yao (é½å°§)
prev parent reply other threads:[~2011-05-27 3:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 20:56 Nathan Froyd
2011-05-27 3:34 ` Yao Qi [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=4DDF1B98.7010002@codesourcery.com \
--to=yao@codesourcery.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).