From: John Snow <jsnow@redhat.com>
To: "Richard Henderson" <richard.henderson@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [gitlab] Renamed issue labels for target architecture
Date: Mon, 14 Jun 2021 11:11:29 -0400 [thread overview]
Message-ID: <b82ba407-ac08-3dfb-2f3c-7677a4352e29@redhat.com> (raw)
In-Reply-To: <0a102843-bb93-93b8-f502-dd0cb2a6c636@linaro.org>
On 6/12/21 6:32 PM, Richard Henderson wrote:
> I've renamed arch:* to target:* as there was some amount of confusion as
> to what "arch" really meant without context. 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.
>
> And then there's the special case of TCI.
>
> Thoughts on these?
>
>
> r~
>
Well, it would have been nice to have been asked first, seeing as I have
done most of the labeling work to sift through issues.
The way the label had been being used was for both the host *and* guest,
because we had thought that fully replicating all architectures for both
host/guest tags wouldn't scale well.
I realize it is helpful to be able to search for the difference between
them, so it's fine -- but it means I have to re-audit all the labels
we've done so far so that they aren't now ... wrong.
--js
next prev parent reply other threads:[~2021-06-14 15:53 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 [this message]
2021-06-14 16:29 ` Philippe Mathieu-Daudé
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=b82ba407-ac08-3dfb-2f3c-7677a4352e29@redhat.com \
--to=jsnow@redhat.com \
--cc=f4bug@amsat.org \
--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.