From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Thomas Huth <thuth@redhat.com>, KVM <kvm@vger.kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Andrew Jones <drjones@redhat.com>,
David Hildenbrand <david@redhat.com>,
Janosch Frank <frankja@linux.ibm.com>,
Nadav Amit <namit@vmware.com>, Liran Alon <liran.alon@oracle.com>,
sean.j.christopherson@intel.com
Subject: Re: A new name for kvm-unit-tests ?
Date: Thu, 30 Jul 2020 08:38:54 +0200 [thread overview]
Message-ID: <682fe35c-f4ea-2540-f692-f23a42c6d56b@de.ibm.com> (raw)
In-Reply-To: <dc518389-945a-1887-7ad0-00ebaf9ae30e@redhat.com>
On 30.07.20 07:41, Thomas Huth wrote:
>
> Hi all,
>
> since Paolo recently suggested to decrease the bus factor for
> kvm-unit-tests [1], I suggested (in a private mail) to maybe also move
> the repo to one of the git forges where we could benefit from a CI
ack.
> system (so that we do not merge bugs so often anymore as it happened in
> the previous months). If we do that step, that might be a good point in
> time to rename the kvm-unit-tests to something more adequate. "Why?" you
> might ask ... well, the unit tests are not only useful for kvm anymore:
I personally dislike renames as you will have old references lurking in
the internet for decades. A rename will result in people continue to using
the old code because the old name is the only thing that they know.
[...]
> Maybe we should come up with a more fancy name for the test suite? For
> example something like "HECATE" - "*H*ypervisor *E*xecution and *C*pu
> instruction *A*dvanced *T*est *E*nvironment" (and Hecate is also the
> goddess of boundaries - which you could translate to the hypervisor
> being the boundary between the virtual and real machine ... with a
> little bit of imagination, of course) ... well, yeah, that's just what
> came to my mind so far, of course. Let's brainstorm ... do you have any
> good ideas for a new name of the kvm-unit-tests? Or do you love the old
> name and think it should stay? Or do you think cpu-unit-tests would be
> the best fit? Please let us know!
If we rename than hecate or cpu-unit-tests is fine for me, but I prefer
to keep the old name.
next prev parent reply other threads:[~2020-07-30 6:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 5:41 A new name for kvm-unit-tests ? Thomas Huth
2020-07-30 6:38 ` Christian Borntraeger [this message]
2020-07-30 7:09 ` David Hildenbrand
2020-07-30 7:13 ` Wanpeng Li
2020-07-30 7:35 ` Paolo Bonzini
2020-07-30 7:50 ` Nadav Amit
2020-07-30 11:32 ` Andrew Jones
2020-07-30 13:33 ` Paolo Bonzini
2020-07-30 17:32 ` Nadav Amit
2020-07-30 17:35 ` Paolo Bonzini
2020-07-30 17:36 ` Nadav Amit
2020-07-31 5:53 ` Thomas Huth
2020-07-31 6:18 ` Andrew Jones
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=682fe35c-f4ea-2540-f692-f23a42c6d56b@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=drjones@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=lvivier@redhat.com \
--cc=namit@vmware.com \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).