From: Tobias Burnus <Tobias_Burnus@mentor.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Labelling of regressions in Bugzilla
Date: Wed, 15 Dec 2021 13:22:41 +0100 [thread overview]
Message-ID: <2f461e1e-f325-9dd6-f0e4-6ea0f9b734a8@mentor.com> (raw)
In-Reply-To: <CAH6eHdSW9op8aCOSVRGbJad175iURKFMZTBjmiWi17Uz08kHLw@mail.gmail.com>
On 15.12.21 12:39, Jonathan Wakely via Gcc wrote:
> Iain pointed out a drawback of not having the regression info in the
> Summary. Currently it does draw your attention when looking at the
> results of a bugzilla search. Andrew noted that bug aliases are
> automatically added to the summary, e.g. https://gcc.gnu.org/PR94404
> shows its alias "(c++core-issues)".
Wouldn't it be easier to click on the "[Change Columns]" button at the
bottom of the search result page and add the new field to the "Selected
Columns"? The known-to-(work/fail) columns are available, i.e. this
feature also works with custom fields.
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
next prev parent reply other threads:[~2021-12-15 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 11:39 Jonathan Wakely
2021-12-15 12:15 ` Richard Earnshaw
2021-12-15 12:24 ` Jonathan Wakely
2021-12-15 12:22 ` Tobias Burnus [this message]
2021-12-15 12:29 ` Jonathan Wakely
2021-12-15 12:43 ` Iain Sandoe
2021-12-15 13:07 ` Jonathan Wakely
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=2f461e1e-f325-9dd6-f0e4-6ea0f9b734a8@mentor.com \
--to=tobias_burnus@mentor.com \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/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).