From: Will Deacon <will.deacon@arm.com>
To: kvm@vger.kernel.org
Cc: Pekka Enberg <penberg@iki.fi>,
Andre Przywara <Andre.Przywara@arm.com>,
Sasha Levin <sasha.levin@oracle.com>,
Cyrill Gorcunov <gorcunov@gmail.com>,
Asias He <asias.hejun@gmail.com>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Marc Zyngier <Marc.Zyngier@arm.com>,
Ronald Minnich <rminnich@google.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
rmk@arm.linux.org.uk
Subject: [ANNOUNCE] Stand-alone kvmtool repository
Date: Wed, 3 Jun 2015 18:25:08 +0100 [thread overview]
Message-ID: <20150603172508.GM17581@arm.com> (raw)
Hi all,
Thanks to a tonne of help (and friendly nagging!) from Andre, I'm
pleased to announce a stand-alone repository for kvmtool:
git://git.kernel.org/pub/scm/linux/kernel/git/will/kvmtool.git
This is a follow-up from a previous thread[1] where we concluded that
this was the right way to go. As requested, the original git history is
preserved but is *not* bisectable since we don't include the kernel tree
in the history. For a bisectable history, the original github repo[2]
should be used instead.
For now, it's living in my area of kernel.org since (a) I already had a
fork there and (b) the patch traffic is pretty low for the project. If
there is sufficient development interest, I can move it somewhere more
appropriate for shared maintenance (e.g. under virt/kvm/).
Anyway, please give it a spin and send patches when it falls over ;)
Will
[1] https://lkml.org/lkml/2015/2/23/393
[2] git://github.com/penberg/linux-kvm.git
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [ANNOUNCE] Stand-alone kvmtool repository
Date: Wed, 3 Jun 2015 18:25:08 +0100 [thread overview]
Message-ID: <20150603172508.GM17581@arm.com> (raw)
Hi all,
Thanks to a tonne of help (and friendly nagging!) from Andre, I'm
pleased to announce a stand-alone repository for kvmtool:
git://git.kernel.org/pub/scm/linux/kernel/git/will/kvmtool.git
This is a follow-up from a previous thread[1] where we concluded that
this was the right way to go. As requested, the original git history is
preserved but is *not* bisectable since we don't include the kernel tree
in the history. For a bisectable history, the original github repo[2]
should be used instead.
For now, it's living in my area of kernel.org since (a) I already had a
fork there and (b) the patch traffic is pretty low for the project. If
there is sufficient development interest, I can move it somewhere more
appropriate for shared maintenance (e.g. under virt/kvm/).
Anyway, please give it a spin and send patches when it falls over ;)
Will
[1] https://lkml.org/lkml/2015/2/23/393
[2] git://github.com/penberg/linux-kvm.git
next reply other threads:[~2015-06-03 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 17:25 Will Deacon [this message]
2015-06-03 17:25 ` [ANNOUNCE] Stand-alone kvmtool repository Will Deacon
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=20150603172508.GM17581@arm.com \
--to=will.deacon@arm.com \
--cc=Andre.Przywara@arm.com \
--cc=Marc.Zyngier@arm.com \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@iki.fi \
--cc=rminnich@google.com \
--cc=rmk@arm.linux.org.uk \
--cc=sasha.levin@oracle.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.