From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Stefan Kangas <stefan@marxist.se>
Cc: "Lars Ingebrigtsen" <larsi@gnus.org>,
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: Tue, 09 Jul 2019 22:06:56 +0100 [thread overview]
Message-ID: <87tvbuzzm7.fsf@tcd.ie> (raw)
In-Reply-To: <CADwFkmmMEWJRTJcf-=71JsVeYL7fh33bSUjyTnTpkPnyADiq7A@mail.gmail.com> (Stefan Kangas's message of "Tue, 9 Jul 2019 19:00:10 +0200")
Stefan Kangas <stefan@marxist.se> writes:
> diff --git a/admin/notes/bug-triage b/admin/notes/bug-triage
> index 2974eee179..1170e29d2e 100644
> --- a/admin/notes/bug-triage
> +++ b/admin/notes/bug-triage
> @@ -104,3 +104,20 @@ according to the communication flow. Red bugs mean that nobody has
> answered, these bugs need primary attention. Green bugs flag that
> there is a recent communication about, and orange bugs flag that the
> bug hasn't been touched for at least two weeks.
> +
> +* Tips and tricks
> +
> +** Show individual bug report in web browser.
> +
> +To see the bug report for Bug#123 in a web browser, visit the URL:
> +
> + https://debbugs.gnu.org/123
> +
> +** Show individual bug report in Emacs.
> +
> +To display the bug report for Bug#123 in emacs:
Nit: The second "emacs" should probably be capitalised.
> + (gnus-read-ephemeral-emacs-bug-group 123)
Is M-x notation preferred? (I don't mind.)
> +This is equivalent to displaying it using the debbugs package above,
> +but only works for individual bug reports.
FWIW, the Debbugs URL format and M-x gnus-read-ephemeral-emacs-bug-group
trick are already described in admin/notes/bugtracker, which is
referenced at the start of bug-triage:
This document just describes the procedure of triaging bugs, for
information on how to work with the bug tracker, see the bugtracker
file in this same directory for the basics. You can also install the
debbugs ELPA package for access to M-x debbugs-gnu, an emacs interface
to debbugs, and M-x debbugs-org, an emacs interface via org-mode.
But I don't mind if bug-triage summarises the same information.
Thanks,
--
Basil
next prev parent reply other threads:[~2019-07-09 21:06 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 [this message]
2019-07-10 0:30 ` Stefan Kangas
2019-07-10 11:45 ` Lars Ingebrigtsen
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=87tvbuzzm7.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=36560@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.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).