From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Christian Bryant <christian@gnulinuxlibre.org>, emacs-devel@gnu.org
Subject: Re: Unanswered Emacs Problem Reports 40+ Months
Date: Fri, 25 Oct 2013 14:47:35 -0400 [thread overview]
Message-ID: <uu61slp4qg.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwviowmlql6.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 24 Oct 2013 10:21:51 -0400")
Stefan Monnier wrote:
> We're not talking about closing the bugs, but confirming that the bug is
> still relevant. Tho, in the absence of a reply by the bug-submitter
> within a month (say), we could also decide to close the bug.
I imagine most responses will be of two kinds:
1) No reply. Then what?
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.)
So I expect the result will be mostly be to annoy the bug reporters.
> The idea is to ask the bug-submitter's help.
Well, ok.
> I think this classification can be made automatically/heuristically
> by checking if the last message was from a developer.
I'm not optimistic that an automatic process can tell us much, but I
guess we'll see.
next prev parent reply other threads:[~2013-10-25 18:47 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 [this message]
2013-10-25 19:03 ` Christian Bryant
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=uu61slp4qg.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).