unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 14192@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#14192: 24.3.50; recursive edit while running ispell not working usefully
Date: Thu, 11 Jan 2024 08:49:57 +0200	[thread overview]
Message-ID: <838r4wmkiy.fsf@gnu.org> (raw)
In-Reply-To: <87mstc5zpt.fsf@web.de> (bug-gnu-emacs@gnu.org)

> Cc: 14192@debbugs.gnu.org
> Date: Thu, 11 Jan 2024 04:13:50 +0100
> From:  Michael Heerdegen via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> Stefan Kangas <stefankangas@gmail.com> writes:
> 
> > If I don't hear back from you within a couple of months, Ill just assume
> > that this has been fixed and close this bug.
> 
> I hope this is not your standard reply.  I mean, ten years, I could have
> died in the meantime, which would not mean that the bug has magically
> disappeared.  I hope you send this kind of text only to people you know
> that are still using Emacs regularly.  Because, if some user asks a
> question, gets no answer, then makes a bug report, and is ignored for
> ten years, it is very unfriendly to request anything at all.  I
> know about the situation of our bug collection, but this is not
> expedient.  You can't expect anyone to even still use Emacs after
> a whole decade.

He said "if I don't hear from you".  If there's no answer and no new
information, leaving bugs open just accumulates bugs that are not (and
cannot be) worked on.  So we made a decision to close such bugs.  If
the issue still exists and affects someone, those persons will
probably report it at some point with enough information to allow
investigating and fixing the problem.

I don't see anything wrong with this policy.  We do know from bitter
experience the downsides of not closing such bugs -- gobs of open bugs
that no one looks at.  That is worse, IMNSHO.





  reply	other threads:[~2024-01-11  6:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12 15:00 bug#14192: 24.3.50; recursive edit while running ispell not working usefully Michael Heerdegen
2013-04-12 16:51 ` Michael Heerdegen
2024-01-10 11:19   ` Stefan Kangas
2024-01-11  3:13     ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11  6:49       ` Eli Zaretskii [this message]
2024-01-11 23:14         ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-13  7:57           ` Stefan Kangas
2024-01-14  1:13             ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11 20:35       ` Stefan Kangas
2024-01-11 23:30         ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12  7:44         ` Eli Zaretskii
2024-01-14  1:25           ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14  6:29             ` Eli Zaretskii
2024-01-16 19:23               ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-16 19:28                 ` Eli Zaretskii
2024-01-27  9:09               ` Eli Zaretskii

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=838r4wmkiy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=14192@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    --cc=stefankangas@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.
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).