unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Xue Fuqiao <xfq.free@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Emacs developers <emacs-devel@gnu.org>,
	Kaushal Modi <kaushal.modi@gmail.com>
Subject: Re: More tags/usertags on Debbugs?
Date: Sun, 10 Jan 2016 13:27:39 +0800	[thread overview]
Message-ID: <CAAF+z6GXXz78rPMi-1fQSERi4ENS+D-P_ejECr18bdSi9JXEjA@mail.gmail.com> (raw)
In-Reply-To: <8760z3qf2t.fsf@gmx.de>

On Sat, Jan 9, 2016 at 5:26 PM, Michael Albinus <michael.albinus@gmx.de> wrote:
> Xue Fuqiao <xfq.free@gmail.com> writes:
>
>> On Sat, Jan 9, 2016 at 10:56 AM, Kaushal Modi <kaushal.modi@gmail.com> wrote:
>>> When I read the severity levels, I actually wondered if we have more than
>>> needed severity tags... How would one distinguish among critical, grave and
>>> serious severities?
>>
>> See https://debbugs.gnu.org/Developer#severities .
>
> We don't use critical and grave. At least not in the debbugs package
> from ELPA.

I found 8 "grave" Emacs bugs, but all of them were filed before April
2012:

https://debbugs.gnu.org/cgi/pkgreport.cgi?package=emacs;archive=both;severity=grave

And I found no "critical" bugs.  So you're right, we almost don't use
these severity levels.



  reply	other threads:[~2016-01-10  5:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-09  2:53 More tags/usertags on Debbugs? Xue Fuqiao
2016-01-09  2:56 ` Kaushal Modi
2016-01-09  3:10   ` Xue Fuqiao
2016-01-09  4:10     ` Kaushal Modi
2016-01-09  9:26     ` Michael Albinus
2016-01-10  5:27       ` Xue Fuqiao [this message]
2016-01-09  7:32   ` Eli Zaretskii
2016-01-11 19:39     ` John Wiegley
2016-01-11 19:57       ` Michael Albinus
2016-01-09  7:24 ` Eli Zaretskii
2016-01-10  5:22   ` Xue Fuqiao

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=CAAF+z6GXXz78rPMi-1fQSERi4ENS+D-P_ejECr18bdSi9JXEjA@mail.gmail.com \
    --to=xfq.free@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=kaushal.modi@gmail.com \
    --cc=michael.albinus@gmx.de \
    /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).