From: Christian Bryant <christian@gnulinuxlibre.org>
To: Glenn Morris <rgm@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Unanswered Emacs Problem Reports 40+ Months
Date: Fri, 25 Oct 2013 12:03:42 -0700 [thread overview]
Message-ID: <526AC08E.3050907@gnulinuxlibre.org> (raw)
In-Reply-To: <uu61slp4qg.fsf@fencepost.gnu.org>
On 10/25/2013 11:47 AM, Glenn Morris wrote:
> I imagine most responses will be of two kinds:
>
> 1) No reply. Then what?
Considering the bugs I will start with are the oldest there,
"no reply" to these bugs will simply produce a note in the
bug that a request for an update was made. Better than
nothing, I think.
> 2) A slightly annoyed "yes, of course my wishlist/doc bug/whatever"
> still applies, didn't you read it/test it/try my patch?".
>
> The useful replies I expect to be a small minority ("It was fixed in
> 24.1", "I misunderstood and this is not actually a bug", etc.)
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
down is both useful for them to better learn Emacs, and to
users who will see that bug maintenance does eventually happen.
> So I expect the result will be mostly be to annoy the bug reporters
I'm open to recommendations for the least annoying verbiage :-)
> I'm not optimistic that an automatic process can tell us much, but I
> guess we'll see.
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.
Cheers!
- CB
next prev parent reply other threads:[~2013-10-25 19:03 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 [this message]
2013-10-26 19:10 ` Glenn Morris
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=526AC08E.3050907@gnulinuxlibre.org \
--to=christian@gnulinuxlibre.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rgm@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.
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).