bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#36560: Adding tags is not proof that anybody actually read the bug r


From: Basil L. Contovounesios
Subject: bug#36560: Adding tags is not proof that anybody actually read the bug report
Date: Tue, 09 Jul 2019 22:06:56 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

Stefan Kangas <address@hidden> 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





reply via email to

[Prev in Thread] Current Thread [Next in Thread]