From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
36560@debbugs.gnu.org, "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Subject: bug#36560: Adding tags is not proof that anybody actually read the bug report
Date: Wed, 10 Jul 2019 13:45:34 +0200 [thread overview]
Message-ID: <m3lfx615b5.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmmynZH+bxx356Qj4qoHta25WT62X+LG13ZDfK-741cF-w@mail.gmail.com> (Stefan Kangas's message of "Wed, 10 Jul 2019 02:30:11 +0200")
Stefan Kangas <stefan@marxist.se> writes:
> The attached patch tries to fix the above two issues by adding a new section
> "How do I read a bug?" to the "Quick-start guide" with both of these methods
> covered.
>
> What do you think?
Looks good to me; applied.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-07-10 11:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 11:49 bug#36560: Add comment when closing bugs to show it was not by accident 積丹尼 Dan Jacobson
2019-07-09 12:02 ` bug#36560: Adding tags is not proof that anybody actually read the bug report 積丹尼 Dan Jacobson
2019-07-09 12:06 ` Lars Ingebrigtsen
2019-07-09 15:10 ` Eli Zaretskii
2019-07-09 15:16 ` 積丹尼 Dan Jacobson
2019-07-09 15:30 ` Eli Zaretskii
2019-07-09 15:31 ` 積丹尼 Dan Jacobson
2019-07-09 15:48 ` Lars Ingebrigtsen
2019-07-09 16:47 ` Stefan Kangas
2019-07-09 16:54 ` Lars Ingebrigtsen
2019-07-09 17:00 ` Stefan Kangas
2019-07-09 21:06 ` Basil L. Contovounesios
2019-07-10 0:30 ` Stefan Kangas
2019-07-10 11:45 ` Lars Ingebrigtsen [this message]
2019-07-09 15:08 ` bug#36560: Add comment when closing bugs to show it was not by accident 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
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=m3lfx615b5.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=36560@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=jidanni@jidanni.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).