From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] PROPOSAL: New 9front Bug Tracker
Date: Thu, 08 Feb 2018 16:54:00 +0000 [thread overview]
Message-ID: <1518108840.141757.1264229208.36F49205@webmail.messagingengine.com> (raw)
In-Reply-To: <20180208090720.GA87033@wopr>
On Thu, Feb 8, 2018, at 9:07 AM, Kurt H Maier wrote:
>
> Bugs shouldn't be prioritized by submitters anyway; they should be
> prioritized by someone else. All bugs are high priority for the person
> reporting the bug. The person fixing the bug should be in charge of
> deciding how quickly that gets done.
I agree with this point. I hate the priority field when reporting a new
bug, especially when i'm not involved with the project. These days
I just ignore it.
--
The lyf so short, the craft so long to lerne. -- Chaucer
next prev parent reply other threads:[~2018-02-08 16:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 1:34 sl
2018-02-08 2:08 ` [9front] " Lyndon Nerenberg
2018-02-08 8:37 ` Julius Schmidt
2018-02-08 9:07 ` Kurt H Maier
2018-02-08 16:54 ` Ethan Grammatikidis [this message]
2018-02-08 23:23 ` Steve Simon
2018-02-08 23:56 ` Kurt H Maier
2018-02-08 2:55 sl
2018-02-09 3:01 sl
2018-02-09 3:15 sl
2018-02-09 3:21 sl
2018-02-09 3:31 sl
2018-02-09 5:11 ` Eli Cohen
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=1518108840.141757.1264229208.36F49205@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--cc=9front@9front.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 NNTP newsgroup(s).