From: Jean Louis <bugs@gnu.support>
To: Lars Ingebrigtsen <larsi@gnus.org>
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, 9 Dec 2020 19:17:20 +0300 [thread overview]
Message-ID: <X9D4kDmnzKsaAsxG@protected.rcdrun.com> (raw)
In-Reply-To: <87v9dbyon9.fsf@gnus.org>
* Lars Ingebrigtsen <larsi@gnus.org> [2020-12-09 18:40]:
> Jean Louis <bugs@gnu.support> writes:
>
> > The workflow to close the bug just because there is no more
> > information about that does not necessarily solve the issue.
>
> The purpose of the Emacs bug tracker is to help Emacs development, not
> for users to keep track of their problems. If it seems unlikely that
> there'll be progress on a bug report, it's closed.
>
> And like I said, if further progress can be made, respond to the report
> at that time, and we'll reopen.
As problem is not personal it is reported to developers. I am am
somebody with good intentions to try to find the cause of that problem
and one month is not enough.
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".
Whatever.
I will definitely try to invoke that bug again.
next prev parent reply other threads:[~2020-12-09 16:17 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 [this message]
2020-12-09 16:48 ` Lars Ingebrigtsen
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=X9D4kDmnzKsaAsxG@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=42374@debbugs.gnu.org \
--cc=larsi@gnus.org \
--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).