public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joseph Myers <jsm28@cam.ac.uk>
To: gcc-gnats@gcc.gnu.org
Cc: jsm28@cam.ac.uk
Subject: web/4857: GNATS followup messages that were not filed
Date: Thu, 01 Nov 2001 13:58:00 -0000 [thread overview]
Message-ID: <E163JZI-0000cR-00@jsm28.trin.cam.ac.uk> (raw)
>Number: 4857
>Category: web
>Synopsis: GNATS followup messages that were not filed
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: gerald
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Nov 12 08:06:02 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: Joseph S. Myers
>Release: 3.1 20011111 (experimental)
>Organization:
none
>Environment:
System: Linux digraph 2.2.20 #2 Sat Nov 10 16:44:22 UTC 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-cvs/configure --prefix=/opt/gcc/mainline --disable-shared --enable-threads=posix --with-system-zlib
>Description:
Between 2001/06/02 18:29:51 UTC (when gnatsweb-2.8.0 was first
imported into GCC CVS, revision 1.30) and 2001/11/12 15:48:07 UTC
(when I fixed the problem, revision 1.42), PR status change messages
generated by gnatsweb did not include gcc-gnats in their recipients.
This meant that replies to those messages did not go to gcc-gnats, and
some PRs may have been wrongly closed for lack of feedback.
For every message to gcc-bugs between those dates that included a PR
number in its Subject line, was not an initial PR submission, and did
not include gcc-gnats in its destination addresses, either the message
or its URL in the web list archives should be sent to the PR to remedy
this. Also, every such closed PR needs to be considered individually
to determine whether, given the unfiled feedback, it should not have
been closed; in particular, any wrongly closed for lack of feedback
must be re-opened.
>How-To-Repeat:
Look at such a PR and find missing feedback sent by an ordinary user
who didn't know that they needed to add gcc-gnats to the addresses
they sent their mail to.
>Fix:
File the messages and re-open PRs as described above.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-11-12 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-01 13:58 Joseph Myers [this message]
2001-11-01 14:46 jsm28
2001-11-01 14:46 jsm28
2001-11-02 4:46 gerald
2001-11-02 6:58 gerald
2002-04-04 10:15 mmitchel
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=E163JZI-0000cR-00@jsm28.trin.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc-gnats@gcc.gnu.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).