all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: new help message in Emacs 25
Date: Thu, 18 Apr 2019 15:45:16 -0400	[thread overview]
Message-ID: <9uy3475c8j.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87pnpjm881.fsf@gmx.de> (Michael Albinus's message of "Thu, 18 Apr 2019 21:19:58 +0200")


>> Then perhaps we ought to send the maintainer, er, the webmaster of
>> [1] a, ehm, "note" asking for a short <p>aragraph, emplaning the
>> reduced Emacs criticality levels, but still show 'em all in one
>> swee</p>?

That would be an inappropriate place to do so, since those are generic
instructions for all the packages using debbugs.gnu.org. Some of them do
use those higher severities. The appropriate place would be

https://debbugs.gnu.org/Emacs.html

But personally I do not think it is worth bothering.

IMO https://debbugs.gnu.org/Reporting.html covers it

    If a report is of a particularly serious bug, or is merely a feature
    request that, you can set the severity level of the bug as you
    report it. This is not required, however, and the developers will
    assign an appropriate severity level to your report if you do not.

AFAIK Emacs has made no deliberate decision to avoid the higher
severities, it is just they very rarely seem applicable/needed.



  reply	other threads:[~2019-04-18 19:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18  0:01 new help message in Emacs 25 Emanuel Berg
2019-04-18  0:38 ` Drew Adams
2019-04-18  0:44   ` Drew Adams
2019-04-18  1:01     ` Emanuel Berg
2019-04-18  1:57       ` Drew Adams
2019-04-18  2:01       ` Noam Postavsky
2019-04-18  5:03         ` Emanuel Berg
2019-04-18  7:59           ` Michael Albinus
2019-04-18 11:12             ` Noam Postavsky
2019-04-18 11:31               ` Michael Albinus
2019-04-18 12:11                 ` Emanuel Berg
2019-04-18 14:18                   ` Noam Postavsky
2019-04-18 17:13                     ` Emanuel Berg
2019-04-18 12:01             ` Emanuel Berg
2019-04-18 19:19               ` Michael Albinus
2019-04-18 19:45                 ` Glenn Morris [this message]
2019-04-18 22:04                   ` Emanuel Berg
2019-04-18  5:03         ` Emanuel Berg
2019-04-18  0:58   ` Emanuel Berg
2019-04-18  2:02     ` Drew Adams
2019-04-18  5:06       ` Emanuel Berg

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=9uy3475c8j.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=help-gnu-emacs@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.