From: Hans-Peter Nilsson <hp@bitrange.com>
To: overseers@sourceware.org
Subject: Re: write access for BINUTILS
Date: Sat, 17 Dec 2011 04:25:00 -0000 [thread overview]
Message-ID: <alpine.BSF.2.00.1112162322470.79680@dair.pair.com> (raw)
(Oops, I edited the recipient list one char too much.)
On Thu, 15 Dec 2011, Ian Lance Taylor wrote:
> Iain Sandoe <developer@sandoe-acoustics.co.uk> writes:
> > 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'd like to add to that, I've seen the forwarded-to address
bounce for gcc.gnu.org addresses because the downstream MX for
the forwarded-to address didn't accept sourceware/gcc.gnu.org as
an injection point, so I'd like to add my +1 to that plea.
(Details to be dug up on request. And if you positively test
that it works today, it might still stop working tomorrow.)
That's so-far three indications against, with two from admins. ;)
brgds, H-P
next reply other threads:[~2011-12-17 4:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 4:25 Hans-Peter Nilsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-26 13:01 write access for: binutils Martin Liška
2011-12-15 14:21 write access for BINUTILS 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
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=alpine.BSF.2.00.1112162322470.79680@dair.pair.com \
--to=hp@bitrange.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).