public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Iain Sandoe <developer@sandoe-acoustics.co.uk>
To: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
Cc: overseers@sourceware.org, nickc@redhat.com, gingold@adacore.com
Subject: Re: write access for BINUTILS
Date: Thu, 15 Dec 2011 18:19:00 -0000	[thread overview]
Message-ID: <C9A2DEFD-4490-4BAD-8058-26991D167667@sandoe-acoustics.co.uk> (raw)
In-Reply-To: <20111215181305.GA17021@ednor.casa.cgf.cx>

Hello Christopher,

On 15 Dec 2011, at 18:13, Christopher Faylor wrote:
> On Thu, Dec 15, 2011 at 09:50:10AM -0800, Ian Lance Taylor wrote:
>> Iain Sandoe <developer@sandoe-acoustics.co.uk> writes:
>>
>>> Do I automatically get an @sourcware.org address?
>>>
>>> If so, then that should also be redirected to the same email address
>>> as for GCC (the return address on this mail).
>>
>> gcc.gnu.org and sourceware.org are the same machine anyhow.
>
> ...but, just to be clear, that doesn't mean that you should be using
> either for general email, as in giving that address out to random  
> third
> parties.  That's not the intent.

I only use my gcc.gnu.org one in ChangeLogs (and the MAINTAINERS file).

Hopefully that's OK? (no-one has so far indicated otherwise)

Presumably it is also more logical to use iains@sourceware.org for  
BINUTILS (than @gcc.gnu.org)?

thanks
Iain

  reply	other threads:[~2011-12-15 18:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15 14:21 Iain Sandoe
2011-12-15 17:50 ` Ian Lance Taylor
2011-12-15 18:04   ` Iain Sandoe
2011-12-15 18:13   ` Christopher Faylor
2011-12-15 18:19     ` Iain Sandoe [this message]
2011-12-16  4:47       ` Ian Lance Taylor
2011-12-17  4:25 Hans-Peter Nilsson
2019-03-26 13:01 write access for: binutils Martin Liška

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=C9A2DEFD-4490-4BAD-8058-26991D167667@sandoe-acoustics.co.uk \
    --to=developer@sandoe-acoustics.co.uk \
    --cc=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=gingold@adacore.com \
    --cc=nickc@redhat.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).