From: Doug Evans <dje@google.com>
To: gdb <gdb@sourceware.org>
Subject: Bugzilla spring cleaning
Date: Thu, 27 Feb 2014 18:11:00 -0000 [thread overview]
Message-ID: <CADPb22RUnsVECKkvu19dvMDnc1xPS6hsR=XQyZdXFw-q6z38uQ@mail.gmail.com> (raw)
Hi.
There's a few cleanups I've wanted to see happen on our Bugzilla site.
The ones that are currently on my mind are these:
1) Remove old entries from the "Versions" list.
Do we really need 3.x and 4.x here?
Personally, I can see deleting 5.x too, and replacing all of them with
a "catch-all" field for old releases.
[I can also see deleting 6.x, but "baby steps" ...]
I can imagine their appearance in some old bug making it
hard/impossible to accomplish this, but I won't know unless I ask.
1b) IWBN to reverse-sort the Versions list.
2) The "Target Milestone" list could also use some trimming.
Comments?
next reply other threads:[~2014-02-27 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 18:11 Doug Evans [this message]
2014-02-28 11:17 ` Pedro Alves
2014-02-28 17:15 ` Doug Evans
2014-02-28 19:57 ` Pedro Alves
2014-02-28 11:45 ` Jan Kratochvil
2014-02-28 17:31 ` Doug Evans
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='CADPb22RUnsVECKkvu19dvMDnc1xPS6hsR=XQyZdXFw-q6z38uQ@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb@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