unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jean Louis <bugs@gnu.support>
Cc: Michael Albinus <michael.albinus@gmx.de>, 42374@debbugs.gnu.org
Subject: bug#42374: 28.0.50; too many tramp messages after computer sleep
Date: Wed, 09 Dec 2020 17:48:42 +0100	[thread overview]
Message-ID: <87r1nzx6vp.fsf@gnus.org> (raw)
In-Reply-To: <X9D4kDmnzKsaAsxG@protected.rcdrun.com> (Jean Louis's message of "Wed, 9 Dec 2020 19:17:20 +0300")

Jean Louis <bugs@gnu.support> writes:

> Development have made to me a strange policy to "close" something what
> is not really closed just because reporter does not follow up or
> cannot replicate it. Instead of swiping the dirt under the carpet
> maybe you should flag the message somehow as "unsolved" rather than
> closed. It gives false statistics and impression as it was not really
> "closed".

The ones that are solved are marked as "fixed".  (Well, in theory.  We
don't actually care.)

I think you misunderstand what the point of a bug tracker and bug triage
is.  "Closed" is just a status, like any other, and it means "it's
unlikely that we'll make more progress here".

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-12-09 16:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15 17:30 bug#42374: 28.0.50; too many tramp messages after computer sleep Jean Louis
2020-07-16  7:34 ` Michael Albinus
2020-07-16  8:39   ` Jean Louis
2020-07-16 11:14     ` Michael Albinus
2020-07-21 12:06       ` Jean Louis
2020-07-21 15:42         ` Michael Albinus
2020-07-24  7:08           ` Jean Louis
2020-10-26 15:49             ` Lars Ingebrigtsen
2020-10-28 12:01               ` Jean Louis
2020-12-09 15:17                 ` Lars Ingebrigtsen
2020-12-09 15:31                   ` Jean Louis
2020-12-09 15:39                     ` Lars Ingebrigtsen
2020-12-09 16:17                       ` Jean Louis
2020-12-09 16:48                         ` Lars Ingebrigtsen [this message]
2020-12-09 17:23                           ` Jean Louis

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=87r1nzx6vp.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=42374@debbugs.gnu.org \
    --cc=bugs@gnu.support \
    --cc=michael.albinus@gmx.de \
    /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).