unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Remove "Recent messages" from `M-x report-emacs-bug'
Date: Mon, 09 May 2016 14:20:17 +0000	[thread overview]
Message-ID: <CAFyQvY0LvgFp0N94CptHuT_oE5rMpyzSP5ScJSX3k5zEYMPB8g@mail.gmail.com> (raw)
In-Reply-To: <87k2j3jq28.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 834 bytes --]

On Mon, May 9, 2016 at 10:15 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:

> Emacs bug reports include the ten most recent lines from the *Messages*
> buffer.  I think that's kinda unfortunate -- there may be private stuff
> there that people are not expecting to share with the world.
>
+1

I also don't like sharing the IP.

The line:

In GNU Emacs 25.0.93.5 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.23)
 of 2016-05-05 built on <IP>.

Is putting the IP there useful?


> And I've never found that data useful when doing bug triage.
>
> Should we remove it from the report?
>

I wouldn't mind that.

Would instead adding `view-lossage` dump help? That way we can see what
commands the user ran to recreate the bug before reporting it. Now
view-lossage also lists the commands corresponding to the bindings.
-- 

-- 
Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 1441 bytes --]

  reply	other threads:[~2016-05-09 14:20 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09 13:53 Remove "Recent messages" from `M-x report-emacs-bug' Lars Ingebrigtsen
2016-05-09 14:20 ` Kaushal Modi [this message]
2016-05-09 14:39   ` Kaushal Modi
2016-05-09 14:46   ` Andreas Schwab
2016-05-09 16:34   ` Eli Zaretskii
2016-05-09 14:44 ` Drew Adams
2016-05-10 15:48   ` Richard Stallman
2016-05-09 16:31 ` Eli Zaretskii
2016-05-09 18:25   ` Lars Ingebrigtsen
2016-05-09 19:09     ` Eli Zaretskii
2016-05-09 19:13       ` Lars Ingebrigtsen
2016-05-09 19:17         ` Dmitry Gutov
2016-05-09 19:25           ` Lars Ingebrigtsen
2016-05-09 19:43             ` Eli Zaretskii
2016-05-09 19:55               ` Lars Ingebrigtsen
2016-05-09 20:13                 ` Lars Ingebrigtsen
2016-05-10 22:37                   ` Glenn Morris
2016-05-09 19:34           ` Kaushal Modi
2016-05-09 19:37             ` Lars Ingebrigtsen
2016-05-09 19:44               ` Kaushal Modi
2016-05-09 19:58                 ` Lars Ingebrigtsen
2016-05-09 20:23                   ` Kaushal Modi
2016-05-09 20:56                     ` Lars Ingebrigtsen
2016-05-09 21:03                       ` Kaushal Modi
2016-05-10 10:06                 ` Rasmus
2016-05-10 12:32           ` Nicolas Richard
2016-05-09 19:40         ` Eli Zaretskii
2016-05-09 20:07           ` Lars Ingebrigtsen
2016-05-09 20:35             ` Drew Adams
2016-05-09 17:32 ` Óscar Fuentes
2016-05-09 18:08   ` Paul Eggert
     [not found] <<87k2j3jq28.fsf@gnus.org>
     [not found] ` <<6ccbf505-5818-432b-98fa-0733930be2e7@default>
     [not found]   ` <<E1b09ty-0002sA-MS@fencepost.gnu.org>
2016-05-10 16:20     ` Drew Adams
2016-05-11  0:08       ` Richard Stallman
     [not found]     ` <<3ad08202-3529-4613-8f78-ef10b3abb9e2@default>
     [not found]       ` <<E1b0HhP-0006Me-VF@fencepost.gnu.org>
2016-05-11 14:44         ` Drew Adams
2016-05-12  0:23           ` Richard Stallman

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=CAFyQvY0LvgFp0N94CptHuT_oE5rMpyzSP5ScJSX3k5zEYMPB8g@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-devel@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).