From: Marek Szuba <marecki@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Change Bugzilla status to IN_PROGRESS when pull request is linked
Date: Sat, 26 Oct 2019 00:09:14 +0100 [thread overview]
Message-ID: <b45561de-dcb1-0f08-cbf5-34fd19b03737@gentoo.org> (raw)
In-Reply-To: <87wocsstmj.fsf@wedjat.horus-it.com>
On 2019-10-25 17:00, Ralph Seichter wrote:
> For convenience, would it be possible to automatically change the status
> of bugs from (UN)CONFIRMED to IN_PROGRESS when Larry The Cow attaches a
> pull request? I tend to forget to change the status myself, and perhaps
> I am not alone in feeling my age in that fashion. ;-)
I am against this, for the same reason as Michał and Kent - to me "in
progress" means "the maintainer is working on it", not "someone has just
made a PR on GitHub which the maintainer may or may not accept".
--
MS
prev parent reply other threads:[~2019-10-25 23:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 16:00 [gentoo-dev] Change Bugzilla status to IN_PROGRESS when pull request is linked Ralph Seichter
2019-10-25 16:09 ` Michał Górny
2019-10-25 16:16 ` Ralph Seichter
2019-10-25 21:44 ` Kent Fredric
2019-10-25 22:51 ` Ralph Seichter
2019-10-25 16:21 ` Mike Gilbert
2019-10-25 23:09 ` Marek Szuba [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=b45561de-dcb1-0f08-cbf5-34fd19b03737@gentoo.org \
--to=marecki@gentoo.org \
--cc=gentoo-dev@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