From: Ian Lance Taylor <ian@airs.com>
To: Iain Sandoe <developer@sandoe-acoustics.co.uk>
Cc: Christopher Faylor
<cgf-use-the-mailinglist-please@sourceware.org>,
overseers@sourceware.org, nickc@redhat.com, gingold@adacore.com
Subject: Re: write access for BINUTILS
Date: Fri, 16 Dec 2011 04:47:00 -0000 [thread overview]
Message-ID: <m3r5059l93.fsf@pepe.airs.com> (raw)
In-Reply-To: <C9A2DEFD-4490-4BAD-8058-26991D167667@sandoe-acoustics.co.uk> (Iain Sandoe's message of "Thu, 15 Dec 2011 18:18:52 +0000")
Iain Sandoe <developer@sandoe-acoustics.co.uk> writes:
> On 15 Dec 2011, at 18:13, Christopher Faylor wrote:
>>
>> ...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)?
It's not ideal even in a ChangeLog entry. I can understand why people
do it, but a real e-mail address is preferred. The point of an e-mail
address in a ChangeLog entry is so that people can send you e-mail, but
we make no promises that we will accept e-mail to @gcc.gnu.org addresses
from outside gcc.gnu.org itself.
I wouldn't switch to @sourceware.org either.
Sorry.
Ian
next prev parent reply other threads:[~2011-12-16 4:47 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
2011-12-16 4:47 ` Ian Lance Taylor [this message]
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=m3r5059l93.fsf@pepe.airs.com \
--to=ian@airs.com \
--cc=cgf-use-the-mailinglist-please@sourceware.org \
--cc=developer@sandoe-acoustics.co.uk \
--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).