From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: 39185@debbugs.gnu.org
Subject: bug#39185: [PATCH] Don't include section "Recent messages" in bug reports
Date: Sun, 19 Jan 2020 11:24:32 -0800 (PST) [thread overview]
Message-ID: <422e79bb-fef0-40af-a61d-f4e3d1093eb9@default> (raw)
In-Reply-To: <87k15ouq36.fsf@marxist.se>
> >> Does anyone object to installing the below patch on master?
> >
> > I do. What if a user wants to include that info in a
> > particular bug report, e.g., where it's relevant?
> > Why not make it easy for a user to include it, even
> > if by default it's excluded?
>
> I don't think that feature request should stop us from moving ahead
> with this potentially serious privacy issue.
It's not about that. It's not about preventing you
from avoiding such privacy problems. It's all about
getting those fixed now. And doing it right, in a
flexible way that covers everything that could - by
users' own determinations - be a privacy issue.
> If someone later wants to re-add an option to include messages, and
> configure the bug reports along the lines you suggest, they are free
> to work on that.
That's the wrong way to deal with this issue, IMO.
It's just punting - kicking the can down the road.
And it's not as if a general solution is somehow
difficult to conceive or hard to implement. Not at
all.
I really don't understand the myopia that narrows the
focus to trying to decide what is _the_ potentially
private info, and then wants to hard-code its exclusion.
prev parent reply other threads:[~2020-01-19 19:24 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
2020-08-18 18:16 ` Lars Ingebrigtsen
2020-01-19 19:24 ` Drew Adams [this message]
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=422e79bb-fef0-40af-a61d-f4e3d1093eb9@default \
--to=drew.adams@oracle.com \
--cc=39185@debbugs.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 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).