From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Richard Henderson <richard.henderson@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>, John Snow <jsnow@redhat.com>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [gitlab] Renamed issue labels for target architecture
Date: Mon, 14 Jun 2021 18:29:50 +0200 [thread overview]
Message-ID: <9b0849bd-20d0-9f72-01bb-ffb60cad575b@amsat.org> (raw)
In-Reply-To: <0a102843-bb93-93b8-f502-dd0cb2a6c636@linaro.org>
On 6/13/21 12:32 AM, Richard Henderson wrote:
> I've renamed arch:* to target:* as there was some amount of confusion as
> to what "arch" really meant without context.
There was a discussion with jsnow about that on IRC, and IIRC he
said what first matters to have easy tags so the reporter does the
first triage directly.
> I've removed labels for
> lm32 and unicore32 which have been removed from qemu 6.1. I've added a
> label for hexagon.
>
> I have not yet added labels for host architecture, because I couldn't
> figure out how best to word the description, or even if all of the
> target:* labels need re-wording to emphasize target.
We want to have a first label to quicker triage. Once a
maintainer is notified, different/finest triage can be done.
The downside is this is noisier for maintainers :(
Wait, are you seeing labels are a notification mechanism or a way
to sort the issues?
Until your rename I was using arch:s390x to contact S390 maintainers
for build failure on s390x host [Build System, arch: s390x], bug in TCG
backend or bug in TCG frontend for target [accel: TCG, arch: s390x],
hoping at least one person notified would have further look.
>
> And then there's the special case of TCI.
For reporters TCI != TCG, so the simplest is "accel: TCI",
but I prefer "accel:TCG:TCI".
next prev parent reply other threads:[~2021-06-14 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-12 22:32 [gitlab] Renamed issue labels for target architecture Richard Henderson
2021-06-13 6:52 ` Stefan Weil
2021-06-14 16:10 ` John Snow
2021-06-14 15:11 ` John Snow
2021-06-14 16:29 ` Philippe Mathieu-Daudé [this message]
2021-06-14 17:03 ` Richard Henderson
2021-06-14 17:18 ` Peter Maydell
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=9b0849bd-20d0-9f72-01bb-ffb60cad575b@amsat.org \
--to=f4bug@amsat.org \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.