From: "William L. Thomson Jr." <wlt-ml@o-sinc.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] The meaning of RESOLVED/UPSTREAM on bugzie
Date: Thu, 30 Mar 2017 14:41:02 -0400 [thread overview]
Message-ID: <assp.026234adb2.2237656.mhd6fq4CsB@wlt> (raw)
In-Reply-To: <20170331073456.50a9157c@katipo2.lan>
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
On Thursday, March 30, 2017 2:34:56 PM EDT Kent Fredric wrote:
>
> _Especially_ when a developer marks a ticket as that without adequate
> explanation as to why.
That sounds like the problem. Do not rely on status/keywords alone. Anytime
those change, a comment should be included as to why. That seems like it would
clear up much of the confusion. Simply do not change status/keywords without a
comment to briefly explain the change and/or usage.
--
William L. Thomson Jr.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2017-03-30 18:41 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. [this message]
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
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=assp.026234adb2.2237656.mhd6fq4CsB@wlt \
--to=wlt-ml@o-sinc.com \
--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