From: "M. J. Everitt" <m.j.everitt@iee.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] The meaning of RESOLVED/UPSTREAM on bugzie
Date: Thu, 30 Mar 2017 18:54:22 +0100 [thread overview]
Message-ID: <bfd2852d-5d6a-703d-c869-c3ea45f58355@iee.org> (raw)
In-Reply-To: <20170330175217.GA4981@whubbs1.gaikai.biz>
[-- Attachment #1.1: Type: text/plain, Size: 985 bytes --]
On 30/03/17 18:52, William Hubbs wrote:
> On Wed, Mar 29, 2017 at 04:15:12PM +0200, Kristian Fiskerstrand wrote:
>> Upstream keyword doesn't seem relevant as it implies having submitted patch or at least filed bug upstream, so the real question is whether we need a separation of something that is out of scope for Gentoo and can be referred upstream or not. The way I see it, directly using RESOLVED INVALID is likely as good an explaination as RESOLVED UPSTREAM unless we want to monitor stats for rejection reasons.
> I disagree with resolved/invalid being appropriate. That means it isn't
> a bug at all. Resolved/upstream should be used when we direct a user to
> file an issue upstream or file the issue ourselves.
>
> Resolved/upstream acknowledges that this is an issue but directs it
> upstream. Resolved/invalid says this isn't an issue.
>
> William
>
I've often thought that "RESO:INVA" is simply tech-speak for "we're not
gonna [investigate] fix that ... "
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-03-30 17:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 7:56 [gentoo-project] The meaning of RESOLVED/UPSTREAM on bugzie Michał Górny
2017-03-29 9:29 ` Marek Szuba
2017-03-29 13:49 ` Paweł Hajdan, Jr.
2017-03-29 14:10 ` Seemant Kulleen
2017-03-29 14:01 ` Ulrich Mueller
2017-03-29 14:15 ` Michał Górny
2017-03-30 17:58 ` William Hubbs
2017-03-30 18:34 ` Kent Fredric
2017-03-30 18:41 ` William L. Thomson Jr.
2017-03-30 18:46 ` Michał Górny
2017-03-30 19:05 ` William L. Thomson Jr.
2017-03-31 13:13 ` Rich Freeman
2017-03-31 14:38 ` William L. Thomson Jr.
2017-03-31 14:45 ` Rich Freeman
2017-04-06 18:14 ` Thomas Deutschmann
2017-03-30 18:50 ` William L. Thomson Jr.
2017-03-30 19:40 ` Kent Fredric
2017-03-30 19:50 ` Kristian Fiskerstrand
2017-03-30 19:58 ` Kent Fredric
2017-03-30 20:49 ` Michał Górny
2017-03-29 14:15 ` Kristian Fiskerstrand
2017-03-30 17:52 ` William Hubbs
2017-03-30 17:54 ` M. J. Everitt [this message]
2017-03-30 17:55 ` Kristian Fiskerstrand
2017-04-01 12:28 ` Andreas K. Huettel
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=bfd2852d-5d6a-703d-c869-c3ea45f58355@iee.org \
--to=m.j.everitt@iee.org \
--cc=gentoo-project@lists.gentoo.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