From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 62320@debbugs.gnu.org
Subject: bug#62320: 30.0.50; Thoughts about (info "(emacs) Bugs")
Date: Wed, 29 Mar 2023 17:19:03 +0200 [thread overview]
Message-ID: <87zg7vwpp4.fsf@web.de> (raw)
In-Reply-To: <83wn374mmn.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 23 Mar 2023 15:34:40 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> I've made some changes in that section, please take a look.
Wow - quite a few!
I've read the whole chapter again and I found nothing that I could
complain about. You also have worked in all my suggestions - apart from
the "if you know how please load relevant Elisp source files before
capturing an Elisp backtrace" one - intentionally?
Apart from that everything looks good, but I'm not able to have an
opinion about some things (like the document structure).
I hope that the requirement to read the chapter carefully and follow all
the rules does not scare people too much (my fear is that the competent
people are more likely to be scared than the incompetent but
self-competent). Dunno if we could try even more to encourage people
without tempting others to spread nonsense. Maybe we could add a
sentence like "If it is sure that you have found a bug, of course we
want to hear about it even if you are not able to follow all of the
advices strictly for some reason. Still, please do your best to take
them into account so that our developers are not required to spend more
time than necessary to understand your report."
Anyway, thanks for revising the chapter and for integrating my
suggestions.
Michael.
next prev parent reply other threads:[~2023-03-29 15:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 5:23 bug#62320: 30.0.50; Thoughts about (info "(emacs) Bugs") Michael Heerdegen
2023-03-21 14:21 ` Eli Zaretskii
2023-03-22 2:21 ` Michael Heerdegen
2023-03-23 13:34 ` Eli Zaretskii
2023-03-29 15:19 ` Michael Heerdegen [this message]
2023-03-29 15:52 ` Eli Zaretskii
2023-03-30 16:08 ` Michael Heerdegen
2023-04-01 10:02 ` Eli Zaretskii
2023-07-20 2:26 ` Michael Heerdegen
2023-07-20 5:02 ` Eli Zaretskii
2023-07-21 2:42 ` Richard Stallman
2023-07-21 5:53 ` Eli Zaretskii
2023-07-23 3:01 ` Richard Stallman
2023-07-21 7:55 ` Michael Albinus
2023-07-23 3:01 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zg7vwpp4.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=62320@debbugs.gnu.org \
--cc=eliz@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.