From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 39185@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>
Subject: bug#39185: [PATCH] Don't include section "Recent messages" in bug reports
Date: Sun, 19 Jan 2020 17:07:09 +0100 [thread overview]
Message-ID: <87ftgbjuqa.fsf@gnus.org> (raw)
In-Reply-To: <83zhejxx80.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 19 Jan 2020 17:49:35 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> I'm not sure I understand what is the general case here. Each part of
> the report that could potentially disclose private information shall
> be identified and dealt with.
There's little in the *Messages* buffer that isn't potentially private.
For instance, here's the last two lines of mine:
nnimap quimby.gnus.org splitting mail...done
nnimap read 6k from quimby.gnus.org
That could be private information. It rather sounds like you're asking
us to get rid of the *Messages* buffer altogether.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-01-19 16:07 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 [this message]
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
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=87ftgbjuqa.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=39185@debbugs.gnu.org \
--cc=eliz@gnu.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.