From: "Frank Ch. Eigler" <fche@elastic.org>
To: overseers@sourceware.org,David Edelsohn
<dje.gcc@gmail.com>,Carlos O'Donell <carlos@redhat.com>
Cc: Overseers <overseers@sourceware.org>,"Joseph S. Myers"
<joseph@codesourcery.com>
Subject: Re: GCC Bugzilla accounts
Date: Wed, 31 May 2017 13:14:00 -0000 [thread overview]
Message-ID: <B6A94E3B-E6D4-47A4-8142-62105235F3AF@elastic.org> (raw)
In-Reply-To: <CAGWvnymuARotq4ZMca0E3fK7+64_aCvKmrK0O3pj9YRWLCFwDg@mail.gmail.com>
On May 31, 2017 8:41:55 AM EDT, David >[...] current requests for account creation
>either are being lost or not responded.
This is not true. Every request that comes into overseers@ gets addressed. We just don't spam you with a visible ack cc.
next prev parent reply other threads:[~2017-05-31 13:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 16:07 David Edelsohn
2017-05-25 16:26 ` Joseph Myers
2017-05-25 16:37 ` Carlos O'Donell
2017-05-25 16:41 ` Joseph Myers
2017-05-25 20:16 ` Ian Lance Taylor
2017-05-25 20:35 ` Gerald Pfeifer
2017-05-25 21:36 ` Frédéric Buclin via overseers
2017-05-31 11:54 ` David Edelsohn
2017-05-31 12:38 ` Carlos O'Donell
2017-05-31 12:41 ` David Edelsohn
2017-05-31 13:14 ` Frank Ch. Eigler [this message]
2017-05-31 13:22 ` David Edelsohn
2017-05-31 14:39 ` Christopher Faylor
2017-05-31 14:49 ` David Edelsohn
2017-06-01 14:19 ` Joseph Myers
2017-06-01 14:44 ` Christopher Faylor
2017-06-01 14:53 ` David Edelsohn
2017-06-01 19:56 ` Christopher Faylor
2017-06-05 15:39 ` David Edelsohn
2017-06-05 15:49 ` Frank Ch. Eigler
2017-06-16 22:02 ` Frank Ch. Eigler
2017-06-17 12:07 ` David Edelsohn
2017-06-20 22:40 ` David Edelsohn
2017-06-21 22:02 ` Frank Ch. Eigler
2017-06-23 13:39 ` David Edelsohn
2017-07-13 18:29 ` David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
2014-12-12 15:53 gcc bugzilla accounts Damien Ruscoe
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=B6A94E3B-E6D4-47A4-8142-62105235F3AF@elastic.org \
--to=fche@elastic.org \
--cc=carlos@redhat.com \
--cc=dje.gcc@gmail.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).