public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Jason Merrill via Overseers <overseers@sourceware.org>
Cc: Jason Merrill <jason@redhat.com>
Subject: Re: gcc.sourceware.org
Date: Fri, 30 Apr 2021 16:42:28 +0000	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2104301638570.235539@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CADzB+2maZ9R3FK1M5xvd+WGZXtCMLVQGBPfy94MZm8Jjgf80YA@mail.gmail.com>

The Bugzilla logic giving extra privileges to @gcc.gnu.org accounts (in 
both GCC and Sourceware Bugzilla) should probably be updated so it also 
gives those privileges to @gcc.sourceware.org accounts.  (If the DNS does 
become a problem, we'll then need to do a bulk change of addresses for all 
@gcc.gnu.org accounts in Bugzilla or subscribed to mailing lists, as well 
as for things that e.g. put an @gcc.gnu.org address as the sender address 
of an outward email, and it may take a while to find all such things to 
update.  But for now, what we can do is simply allow @gcc.sourceware.org 
to be used interchangably with @gcc.gnu.org, in email addresses as well as 
for website accesses.)

-- 
Joseph S. Myers
joseph@codesourcery.com

  parent reply	other threads:[~2021-04-30 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30  4:23 gcc.sourceware.org Jason Merrill
2021-04-30 15:54 ` gcc.sourceware.org Christopher Faylor
2021-04-30 16:42 ` Joseph Myers [this message]
2021-05-01  3:07   ` gcc.sourceware.org Carlos O'Donell
2021-05-01  3:17     ` gcc.sourceware.org Jason Merrill
2021-05-01  4:19       ` gcc.sourceware.org Carlos O'Donell

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.DEB.2.22.394.2104301638570.235539@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=jason@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).