From: Sergei Trofimovich <slyfox@gentoo.org>
To: bman@gentoo.org, gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] On dropping sparc@ from CC on bugs
Date: Mon, 11 Sep 2017 08:43:13 +0100 [thread overview]
Message-ID: <20170911084313.2cf9f40e@sf> (raw)
In-Reply-To: <bug-621130-3398-g5w8kj8DWg@http.bugs.gentoo.org/>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
On Sun, 10 Sep 2017 22:18:08 +0000
bugzilla-daemon@gentoo.org wrote:
> DO NOT REPLY TO THIS EMAIL. Also, do not reply via email to the person
> whose email is mentioned below. To comment on this bug, please visit:
>
> https://bugs.gentoo.org/show_bug.cgi?id=621130
>
> Aaron Bauman <bman@gentoo.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC|sparc@gentoo.org |
>
> --- Comment #16 from Aaron Bauman <bman@gentoo.org> ---
> sparc was dropped to exp.
>
> https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b5901d8f716555a1479f12313a2925fcadd177a9
[ CCed gentoo-dev@ to raise general awareness ]
Why do you need to drop sparc@ from CC on all the bugs?
It takes away possibility from users using sparc@ to report
test status easily. Even after the bug is closed.
sh@ and s390@ are also exp profiles and CC is one of mechanisms
to ask arch teams to try keywording/stablereq.
--
Sergei
[-- Attachment #2: Цифровая подпись OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next parent reply other threads:[~2017-09-11 7:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-621130-3398@http.bugs.gentoo.org/>
[not found] ` <bug-621130-3398-g5w8kj8DWg@http.bugs.gentoo.org/>
2017-09-11 7:43 ` Sergei Trofimovich [this message]
2017-09-11 22:07 ` [gentoo-dev] Re: On dropping sparc@ from CC on bugs Aaron Bauman
2017-09-13 1:26 ` Matt Turner
2017-09-13 7:00 ` Ulrich Mueller
2017-09-13 8:03 ` Sergei Trofimovich
2017-09-14 2:44 ` Yury German
2017-09-14 7:28 ` Sergei Trofimovich
2017-09-23 20:04 ` Sergei Trofimovich
2017-10-13 10:09 ` Sergei Trofimovich
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=20170911084313.2cf9f40e@sf \
--to=slyfox@gentoo.org \
--cc=bman@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