From: Nadav Amit <nadav.amit@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>, Thomas Huth <thuth@redhat.com>
Subject: Re: New repo for kvm-unit-tests
Date: Fri, 31 Jul 2020 09:07:44 -0700 [thread overview]
Message-ID: <A0556EC0-1975-4DBD-9A9B-3A9B8FE24FC7@gmail.com> (raw)
In-Reply-To: <7040f939-3f15-e56c-61dd-201ec46b6515@redhat.com>
> On Jul 30, 2020, at 3:05 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> kvm-unit-tests now lives at its now home,
> https://gitlab.com/kvm-unit-tests/kvm-unit-tests. The kernel.org
> repository has been retired.
>
> Nothing else changes, we're still living in the 20th century for patch
> submission and issue tracking.
>
> Thanks Thomas for your work and your persistence! I must admit it
> really just works.
Can you update http://www.linux-kvm.org/page/KVM-unit-tests so when
someone googles KVM-unit-tests he will get the right repository?
next prev parent reply other threads:[~2020-07-31 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 22:05 New repo for kvm-unit-tests Paolo Bonzini
2020-07-31 16:07 ` Nadav Amit [this message]
2020-08-01 11:25 ` 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=A0556EC0-1975-4DBD-9A9B-3A9B8FE24FC7@gmail.com \
--to=nadav.amit@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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).