From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 39185@debbugs.gnu.org, stefan@marxist.se
Subject: bug#39185: [PATCH] Don't include section "Recent messages" in bug reports
Date: Tue, 18 Aug 2020 19:31:52 +0300 [thread overview]
Message-ID: <83v9hfewzr.fsf@gnu.org> (raw)
In-Reply-To: <87lfichr24.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 18 Aug 2020 18:11:47 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Stefan Kangas <stefan@marxist.se>, 39185@debbugs.gnu.org,
> drew.adams@oracle.com
> Date: Tue, 18 Aug 2020 18:11:47 +0200
>
> The proposal is to not include any output from the *Messages* buffer. I
> have never found that data interesting when doing bug triage, and it's a
> potentially severe privacy violation.
>
> Is it your stance that you don't want to change this behaviour? If so,
> I'll close this bug report.
My opinion on this is that we slowly but consistently give up more and
more useful debugging information due to privacy considerations.
However, I seem to be the odd one out here, so feel free to disregard
my opinion on this matter.
next prev parent reply other threads:[~2020-08-18 16:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 23:58 bug#39185: [PATCH] Don't include section "Recent messages" in bug reports Stefan Kangas
2020-01-19 2:21 ` Drew Adams
2020-01-19 2:39 ` Stefan Kangas
2020-01-19 15:13 ` Eli Zaretskii
2020-01-19 15:27 ` Stefan Kangas
2020-01-19 15:49 ` Eli Zaretskii
2020-01-19 16:07 ` Lars Ingebrigtsen
2020-01-19 16:43 ` Eli Zaretskii
2020-01-19 16:47 ` Lars Ingebrigtsen
2020-01-19 17:10 ` Stefan Kangas
2020-01-19 19:20 ` Drew Adams
2020-01-20 12:33 ` Dmitry Gutov
2020-08-18 16:11 ` Lars Ingebrigtsen
2020-08-18 16:31 ` Eli Zaretskii [this message]
2020-08-18 18:16 ` Lars Ingebrigtsen
2020-01-19 19:24 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83v9hfewzr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39185@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.