unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <rms@gnu.org>, "'Stephen J. Turnbull'" <stephen@xemacs.org>
Cc: acm@muc.de, emacs-devel@gnu.org
Subject: RE: please review bug #13141
Date: Sun, 20 Jan 2013 13:21:34 -0800	[thread overview]
Message-ID: <43F5E102C96D463EB05CCF2B31927861@us.oracle.com> (raw)
In-Reply-To: <E1TwzpU-0007Of-Pd@fencepost.gnu.org>

>     I've had at least half a dozen cases
>     where users deleted automatically added information which I then
>     requested -- to no avail, since the reporters never responded.
> 
> To go out of their way to delete it makes me wonder why.  Maybe it was
> a valid reason.  Could it be that there was something private in that
> information which they specifically did not want to send?
> 
> Because of this consideration it would not be right to hide
> that information.  We should not try to trick our users into sending
> us something they did not want to send.

That is one valid reason a user might not want to send some information.

And a valid reason for Emacs not to hide it.  And a good reason to give users an
easy way to (a) not include it by default but also perhaps (b) be able to add
any piece of it by hitting a key.

Some have pointed out that the default set of info to include is one thing,
whether hard-coded or user customizable, but it is also the case that one often
wants to tailor the info sent to the particular bug.

A user who reports many bugs for which most of the default info is not pertinent
(just noise) can customize the option to get a different default set, as an
alternative to deleting the noise manually each time.

But it would be good to also let that user add this or that info quickly, when
relevant.  That is where (b) can come in (suggested by Dmitry).  The patch I
sent does not provide (b).  But it should be simple to do that.




  reply	other threads:[~2013-01-20 21:21 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-19 23:10 please review bug #13141 Drew Adams
2013-01-19 23:20 ` Alan Mackenzie
2013-01-19 23:59   ` Drew Adams
2013-01-20  0:12     ` Xue Fuqiao
2013-01-20  7:16     ` Stephen J. Turnbull
2013-01-20 10:33       ` Xue Fuqiao
2013-01-20 17:08       ` Eli Zaretskii
2013-01-20 18:41       ` bug#13141: " Richard Stallman
2013-01-20 21:21         ` Drew Adams [this message]
2013-01-21  1:03         ` Dmitry Gutov
2013-01-21  3:02           ` Stephen J. Turnbull
2013-01-21  3:26           ` Stephen J. Turnbull
2013-01-21  2:39         ` Stephen J. Turnbull
2013-01-20 10:50     ` Alan Mackenzie
2013-01-20 12:02       ` Xue Fuqiao
2013-01-20 20:27         ` Glenn Morris
2013-01-21  2:52           ` Stephen J. Turnbull
2013-01-20 17:40       ` Drew Adams
2013-01-21  4:24         ` Drew Adams
2013-01-19 23:21 ` Drew Adams
  -- strict thread matches above, loose matches on Subject: below --
2013-01-21  7:18 Andrey Paramonov
2013-01-21 15:05 ` Drew Adams
2013-01-21 15:26   ` Harald Hanche-Olsen
2013-01-21 17:29     ` Eli Zaretskii
2013-01-21 22:20     ` Drew Adams
2013-01-22  4:15       ` Xue Fuqiao
2013-01-22  6:40         ` Drew Adams
2013-01-22  7:51           ` Xue Fuqiao
2013-01-22 15:10             ` 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=43F5E102C96D463EB05CCF2B31927861@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=stephen@xemacs.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).