From: Glenn Morris <rgm@gnu.org>
To: Christian Bryant <christian@gnulinuxlibre.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Unanswered Emacs Problem Reports 40+ Months
Date: Sat, 26 Oct 2013 15:10:04 -0400 [thread overview]
Message-ID: <ysy55frgqb.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 526AC08E.3050907@gnulinuxlibre.org
Christian Bryant wrote:
> I will shoot a handy report every 50-100 bugs over to Stefan
> with those who answered with a slightly annoyed "yes". Taking
> those in chunks and having new Emacs team members whittle them
^^^^^^^^^^^^^^^^^^^^^^
I'm not aware that there are any such people with interest in dealing
with long-standing bug reports.
> I've performed tasks like this many times at work, for the same
> reasons: I saw a report where a specific application or library
> not only dominated the bug report, but had the oldest bugs, too.
> Maybe a year from now, or two or three years from now, some other
> application can take that honor.
Up until a little over 40 months ago, no-one other than Emacs was using
debbugs.gnu.org, so the fact that almost all very old open bugs are
Emacs ones tells us nothing. Sources such as
http://debbugs.gnu.org/rrd/emacs.html are more informative.
BTW, there's no point querying anything tagged "confirmed" or "help"
(not that many things are), or "wontfix". Things with severity
"wishlist" or higher than "normal" are quite likely to still be
applicable (actually, I suppose, maybe, anything with severity !=
"normal"). Things tagged "moreinfo" are likely to ... need more
information.
prev parent reply other threads:[~2013-10-26 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 3:46 Unanswered Emacs Problem Reports 40+ Months Christian Bryant
2013-10-24 7:46 ` Glenn Morris
2013-10-24 7:59 ` Christian Bryant
2013-10-24 14:21 ` Stefan Monnier
2013-10-25 18:47 ` Glenn Morris
2013-10-25 19:03 ` Christian Bryant
2013-10-26 19:10 ` Glenn Morris [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ysy55frgqb.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=christian@gnulinuxlibre.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).