From: Eli Zaretskii <eliz@gnu.org>
To: Daiki Ueno <ueno@gnu.org>
Cc: michael_heerdegen@web.de, 27445@debbugs.gnu.org
Subject: bug#27445: 26.0.50; Insufficient documentation for pinentry.el
Date: Fri, 24 Nov 2017 17:41:41 +0200 [thread overview]
Message-ID: <83609zadl6.fsf@gnu.org> (raw)
In-Reply-To: <od1tvxjwwdu.fsf-ueno@gnu.org> (message from Daiki Ueno on Fri, 24 Nov 2017 16:04:45 +0100)
> From: Daiki Ueno <ueno@gnu.org>
> Cc: michael_heerdegen@web.de, 27445@debbugs.gnu.org
> Date: Fri, 24 Nov 2017 16:04:45 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Please don't use such language here, certainly not when replying to
> > legitimate bug reports.
>
> Legitimate bug reports should report the root problem to the relevant
> project (GnuPG or Debian), instead of insisting on documenting a broken
> behavior inherently caused by an external factor.
Feel free to point that out, but without insulting the people who
report problems here. We don't want to discourage users from
reporting issues because they are afraid of being publicly humiliated.
next prev parent reply other threads:[~2017-11-24 15:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 4:29 bug#27445: 26.0.50; Insufficient documentation for pinentry.el Michael Heerdegen
2017-10-26 12:00 ` Michael Heerdegen
2017-10-28 9:13 ` Eli Zaretskii
2017-11-18 9:50 ` Eli Zaretskii
2017-11-19 7:07 ` Daiki Ueno
2017-11-20 17:55 ` Andy Moreton
2017-11-21 12:15 ` Daiki Ueno
2017-11-21 15:56 ` Eli Zaretskii
2017-11-21 19:59 ` Daiki Ueno
2017-11-22 15:46 ` Eli Zaretskii
2017-11-22 16:18 ` Daiki Ueno
2017-11-23 1:06 ` Michael Heerdegen
2017-11-23 5:08 ` Daiki Ueno
2017-11-24 7:04 ` Michael Heerdegen
2017-11-24 10:49 ` Daiki Ueno
2017-11-24 13:40 ` Eli Zaretskii
2017-11-24 15:04 ` Daiki Ueno
2017-11-24 15:41 ` Eli Zaretskii [this message]
2017-11-24 17:54 ` Richard Stallman
2017-11-20 19:33 ` Michael Heerdegen
2017-11-21 6:19 ` Daiki Ueno
2017-11-27 22:12 ` diego
2017-12-12 9:19 ` Rasmus
2017-12-22 9:49 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83609zadl6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27445@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=ueno@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.