From: Jonathan Larmour <jifl@jifvik.org>
To: Brooks Moses <brooks@codesourcery.com>
Cc: overseers@sourceware.org
Subject: Re: Request for commit access to sourceware src/ tree.
Date: Mon, 12 Nov 2007 11:29:00 -0000 [thread overview]
Message-ID: <473838FA.5070100@jifvik.org> (raw)
In-Reply-To: <4737E383.30702@codesourcery.com>
Brooks Moses wrote:
>
> My understanding is that this should be relatively simple to do since I
> already have commit access to the GCC source repository, under the
> account name of brooks@gcc.gnu.org.
Yep, it's easy and is now done.
> (Also, while you're poking at that account -- it's probably still linked
> to bmoses@stanford.edu for any email it gets. That address is going
> away, and so the account should now be linked to brooks@codesourcery.com
> instead. Could you also take care of that for me?)
Actually it's linked to bmoses [at] dpdx.net. Do you still want it changed?
Jifl
--
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
next prev parent reply other threads:[~2007-11-12 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 5:24 Brooks Moses
2007-11-12 11:29 ` Jonathan Larmour [this message]
2007-11-12 17:20 ` Brooks Moses
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=473838FA.5070100@jifvik.org \
--to=jifl@jifvik.org \
--cc=brooks@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).