From: David Bremner <david@tethera.net>
To: rms@gnu.org, Glenn Morris <rgm@gnu.org>
Cc: 18900@debbugs.gnu.org
Subject: bug#18900: 24.4; please don't include view-lossage in bug reports by default
Date: Sat, 01 Nov 2014 17:02:45 +0100 [thread overview]
Message-ID: <87sii2hpsq.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <E1XkaER-0001xh-9J@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
>
> Are you thinking of a reproducible bug? It isn't needed for them. It
> is meant to be useful for irreproducible bugs, if the user runs
> report-emacs-bug right away.
>
> To make it possible to ask for those data later, they have to be
> saved. We could make report-emacs-bug save them in a file
> in case they are asked for.
I'd worry a bit about similar issues with writing sensitive information
to disk in clear text. Although this is almost certainly less severe of
a problem than sending the same information to a public mailing list, it
still doesn't seem like a good default to me.
What about a seperate function "report-bug-with-key-log" so that the
user has to consciously make a choice to send this information? One can
of course debate about the name, I would just prefer transparency to
tradition here.
Cheers,
David
next prev parent reply other threads:[~2014-11-01 16:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 7:55 bug#18900: 24.4; please don't include view-lossage in bug reports by default David Bremner
2014-10-30 15:35 ` Glenn Morris
2014-10-31 19:13 ` Stefan Monnier
2014-11-01 15:04 ` Richard Stallman
2014-11-01 16:02 ` David Bremner [this message]
2014-11-01 17:07 ` Glenn Morris
2014-11-02 4:57 ` Richard Stallman
2014-11-02 17:41 ` Glenn Morris
2014-11-03 2:29 ` Stefan Monnier
2014-11-04 7:07 ` Glenn Morris
2014-11-05 15:47 ` Eli Zaretskii
2014-11-05 16:47 ` Glenn Morris
2014-11-05 17:07 ` 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=87sii2hpsq.fsf@maritornes.cs.unb.ca \
--to=david@tethera.net \
--cc=18900@debbugs.gnu.org \
--cc=rgm@gnu.org \
--cc=rms@gnu.org \
/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).