[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <12F471C8-2CF3-4CD7-B417-C8CC898669E6@mit.edu>
Date: Mon, 7 Nov 2011 18:42:47 -0500
From: Theodore Tso <tytso@....EDU>
To: Anthony Liguori <anthony@...emonkey.ws>
Cc: Theodore Tso <tytso@....edu>, Pekka Enberg <penberg@...nel.org>,
Vince Weaver <vince@...ter.net>, Avi Kivity <avi@...hat.com>,
"kvm@...r.kernel.org list" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>,
qemu-devel Developers <qemu-devel@...gnu.org>,
Alexander Graf <agraf@...e.de>,
Blue Swirl <blauwirbel@...il.com>,
Américo Wang <xiyou.wangcong@...il.com>,
Ingo Molnar <mingo@...e.hu>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [Qemu-devel] [PATCH] KVM: Add wrapper script around QEMU to test kernels
On Nov 7, 2011, at 5:19 PM, Anthony Liguori wrote:
>
> The kernel ecosystem does not have to be limited to linux.git. There could be a process to be a "kernel.org project" for projects that fit a certain set of criteria. These projects could all share the Linux kernel release cadence and have a kernel maintainer as a sponsor or something like that.
>
> That is something that could potentially benefit things like e2fs-tools and all of the other tools that are tied closely to the kernel.
We have that already. Packages such as e2fsprogs, xfsprogs, xfstests, sparse, git, etc., have git trees under git.kernel.org. And I agree that's the perfect place for kvm-tool and perf. :-)
-- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists