unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <moasenwood@zoho.eu>
To: help-gnu-emacs@gnu.org
Subject: Re: new help message in Emacs 25
Date: Thu, 18 Apr 2019 07:03:07 +0200	[thread overview]
Message-ID: <86v9zb7vn8.fsf@zoho.eu> (raw)
In-Reply-To: CAM-tV--rcDKWgMg0FeRuMtnSbsxVULsdbzN7nWsjLw2HUqFBdQ@mail.gmail.com

Noam Postavsky wrote:

> You can set the severity by starting your
> report with the line
>
> Severity: minor
>
> See
> https://debbugs.gnu.org/Reporting.html#severities

Thanks, you seem to be quite right: it is
nothing less than a "pseudo-header" :) [1]

Here are the different severity levels one can
assign it according to RFC I mean this URL. [2]

    critical
    grave
    serious
    important
    normal
    minor
    wishlist

I can't wait to find another bug and put
pseudo-header on my hacker resume! :)


[1] https://debbugs.gnu.org/Reporting.html#pseudoheader
[2] https://debbugs.gnu.org/Developer.html#severities

-- 
underground experts united
http://user.it.uu.se/~embe8573




  reply	other threads:[~2019-04-18  5:03 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 [this message]
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
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

  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=86v9zb7vn8.fsf@zoho.eu \
    --to=moasenwood@zoho.eu \
    --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. 
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).