public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: overseers@sourceware.org
Subject: Re: move bugzilla account request email to another list?
Date: Thu, 1 Sep 2022 13:35:20 -0400	[thread overview]
Message-ID: <07505d42-2cf9-1eb5-6c6c-231957803ac5@redhat.com> (raw)
In-Reply-To: <20220901163010.4v2i6qi5jwhjfib4@cgf.cx>

On 9/1/22 12:30, Christopher Faylor via Overseers wrote:
> I think we've reached the point where the bugzilla account request email
> should be moved to another list.  As it stands now, I have a tendency
> to ignore this list because most of the traffic does not really pertain
> to overseeing sourceware.org.
> 
> Could we move these requests elsewhere and maybe even automate them?

Moving them to another list is a good idea.

I wonder if we can't queue them up for handling in some way?

-- 
Cheers,
Carlos.


  reply	other threads:[~2022-09-01 17:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 16:30 Christopher Faylor
2022-09-01 17:35 ` Carlos O'Donell [this message]
2022-09-01 17:42   ` Christopher Faylor
2022-09-02 10:32 ` Mark Wielaard
2022-09-02 14:50   ` Christopher Faylor
2022-09-02 14:58     ` Carlos O'Donell
2022-09-02 21:09       ` Mark Wielaard

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=07505d42-2cf9-1eb5-6c6c-231957803ac5@redhat.com \
    --to=carlos@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).