public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: Overseers mailing list <overseers@sourceware.org>,
	Joseph Myers <joseph@codesourcery.com>
Subject: Re: gcc.sourceware.org
Date: Sat, 1 May 2021 00:19:00 -0400	[thread overview]
Message-ID: <2379c47c-891e-3d63-75b6-59ea4d3bd1b6@redhat.com> (raw)
In-Reply-To: <CADzB+2nYkg7kC0Y5xgGEQNHAsu6vy3gNLWpmN2jP4+wixQjV5w@mail.gmail.com>

On 4/30/21 11:17 PM, Jason Merrill wrote:
> On Fri, Apr 30, 2021 at 11:07 PM Carlos O'Donell <carlos@redhat.com> wrote:
>>
>> On 4/30/21 12:42 PM, Joseph Myers via Overseers wrote:
>>> 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.)
>>
>> I have completed the setup for gcc.sourceware.org. Please verify it meets
>> your requirements.
>>
>> I am working on the bugzilla change.
> 
> Looking good, thanks.

All bugzilla group User regexps have been updated (6 of them).

The old regexp was: \@gcc\.gnu\.org$
The new regexp is: \@gcc\.(?:sourceware|gnu)\.org$

Postfix is also updated to allow mail to gcc.sourceware.org.

-- 
Cheers,
Carlos.


      reply	other threads:[~2021-05-01  4:19 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 ` gcc.sourceware.org Joseph Myers
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       ` Carlos O'Donell [this message]

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=2379c47c-891e-3d63-75b6-59ea4d3bd1b6@redhat.com \
    --to=carlos@redhat.com \
    --cc=jason@redhat.com \
    --cc=joseph@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).