all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Andreas Rottmann <a.rottmann@gmx.at>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: where to send patches
Date: Wed, 09 Mar 2011 15:31:25 -0500	[thread overview]
Message-ID: <n48vwonihu.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87sjuwjb41.fsf@stupidchicken.com> (Chong Yidong's message of "Wed, 09 Mar 2011 15:24:30 -0500")

Chong Yidong wrote:

>> I did think about adding "Severity: normal" to the M-x report-emacs-bug
>> boilerplate, and inviting people to adjust it if they wished. But maybe
>> it makes reporting more complicated for little gain?
>
> It should be for Emacs developers to decide bug severity, not the
> reporters.

Ultimately, yes, but people can suggest what they think the severity
should be. Minor for a doc typo, wishlist for a feature (anything with
"feature request" etc in the subject is automatically classified as
wishlist), important for a crash, etc. They have been able to do this
for as long as we have been using debbugs. But I agree that it is not
hugely helpful by itself.



  reply	other threads:[~2011-03-09 20:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-26 17:32 [PATCH] Allow passing frame parameters to emacsclient Andreas Rottmann
2011-03-07 21:44 ` where to send patches [was Re: [PATCH] Allow passing frame parameters to emacsclient] Glenn Morris
2011-03-07 22:29   ` Andreas Rottmann
2011-03-08  2:05   ` Stefan Monnier
2011-03-09 19:50     ` where to send patches Glenn Morris
2011-03-09 20:24       ` Chong Yidong
2011-03-09 20:31         ` Glenn Morris [this message]
2011-03-10  2:26       ` Stefan Monnier
2011-03-20 23:06         ` Wojciech Meyer

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=n48vwonihu.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=a.rottmann@gmx.at \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.