public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Benjamin Kosnik <bkoz@redhat.com>
To: Douglas Gregor <doug.gregor@gmail.com>
Cc: overseers@gcc.gnu.org
Subject: Re: Requesting write access to GCC CVS repository
Date: Thu, 17 Feb 2005 19:54:00 -0000	[thread overview]
Message-ID: <20050216123459.25a2005b@belmont.artheist.org> (raw)
In-Reply-To: <200502141247.31742.doug.gregor@gmail.com>


> I have had access previously, with the account name dgregor and e-mail address 
> dgregor@apple.com.  However, my e-mail address has changed and I no longer 
> have the SSH keys for the dgregor account. Thank you.

Hey folks, what is the best way to proceed here? Can Doug just send in
re-generated ssh keys, and can the dgregor account be re-pointed to his
new email? That seems to be the simplest way to handle this.

best,
benjamin

  reply	other threads:[~2005-02-16 18:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-17 19:45 Douglas Gregor
2005-02-17 19:54 ` Benjamin Kosnik [this message]
2005-02-17 19:58   ` Ian Lance Taylor
2005-02-22 20:21     ` Doug Gregor
2005-02-27 14:45       ` Ian Lance Taylor

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=20050216123459.25a2005b@belmont.artheist.org \
    --to=bkoz@redhat.com \
    --cc=doug.gregor@gmail.com \
    --cc=overseers@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).