unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
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 17:49:35 +0200	[thread overview]
Message-ID: <83zhejxx80.fsf@gnu.org> (raw)
In-Reply-To: <87tv4rtqj2.fsf@marxist.se> (message from Stefan Kangas on Sun, 19 Jan 2020 16:27:45 +0100)

> From: Stefan Kangas <stefan@marxist.se>
> Cc: 39185@debbugs.gnu.org,  drew.adams@oracle.com
> Date: Sun, 19 Jan 2020 16:27:45 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > The right way of dealing with these issues is to hide the parts which
> > could breach the privacy by converting the characters there into
> > something like "xxx" or "***", and leave the rest of the information
> > intact.
> 
> How would you propose to do that in the general case?

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.





  reply	other threads:[~2020-01-19 15:49 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 [this message]
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

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=83zhejxx80.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).