From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] The meaning of RESOLVED/UPSTREAM on bugzie
Date: Sat, 01 Apr 2017 14:28:55 +0200 [thread overview]
Message-ID: <2467653.CYrqeRgP7b@pinacolada> (raw)
In-Reply-To: <1490774199.1744.1.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
> How would you feel about removing/disabling the UPSTREAM resolution,
Right now there is no agreement on what RESOLVED UPSTREAM is supposed to mean,
and everybody is using it in a different sense. Nothing in this thread
indicates any effective measures to improve that.
So, yes I'm for removing it.
My advice for serious upstream bugs that Gentoo can't do much about is to
1) keep the Gentoo bug open until it's fixed
2) add a whiteboard note like "[tracking upstream]"
3) and linking the upstream bug report in URL
If there is no upstream bug, make one or ask the reporter to make one and link
to it (resolved needinfo in the meantime if needed).
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
prev parent reply other threads:[~2017-04-01 12:29 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
2017-03-30 17:55 ` Kristian Fiskerstrand
2017-04-01 12:28 ` Andreas K. Huettel [this message]
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=2467653.CYrqeRgP7b@pinacolada \
--to=dilfridge@gentoo.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