From: Christoph Hellwig <hch@infradead.org>
To: Avi Kivity <avi@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Anthony Liguori <anthony@codemonkey.ws>,
KVM list <kvm@vger.kernel.org>
Subject: Re: Split kvm source tarballs
Date: Wed, 25 Mar 2009 14:17:16 -0400 [thread overview]
Message-ID: <20090325181716.GA3215@infradead.org> (raw)
In-Reply-To: <49CA71C8.3000407@redhat.com>
On Wed, Mar 25, 2009 at 08:02:48PM +0200, Avi Kivity wrote:
> So how about this:
>
> - keep copies of the headers in the qemu repository. 'make sync' becomes
> a maintainer tool rather than a developer tool
Yeah. That similar how we maintain the headers and some shared source
file for XFS and libxfs in xfsprogs.
> - move qemu to the root of the repository, and reparent libkvm/ user/
> and friends under it. this will give us easier merging.
Yeah. While you're at it user/ might be renamed to something more
descriptive.
> - move the external module kit into kvm.git
As in your kvm development kernel tree? Not sure it's a good idea
to suck this into a full kernel tree. Probably worth making it a small
repository of it's own.
next prev parent reply other threads:[~2009-03-25 18:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 14:21 Split kvm source tarballs Avi Kivity
2009-03-25 13:18 ` Anthony Liguori
2009-03-25 13:23 ` Avi Kivity
2009-03-25 13:44 ` Anthony Liguori
2009-03-25 16:47 ` Christoph Hellwig
2009-03-25 18:02 ` Avi Kivity
2009-03-25 18:17 ` Christoph Hellwig [this message]
2009-03-26 9:09 ` Avi Kivity
2009-03-26 22:48 ` Christoph Hellwig
2009-04-16 20:17 ` Christoph Hellwig
2009-04-18 22:13 ` Anthony Liguori
2009-04-19 8:26 ` Avi Kivity
2009-03-25 21:34 ` Anthony Liguori
2009-03-26 8:57 ` Christoph Hellwig
2009-03-26 18:19 ` Anthony Liguori
2009-03-26 22:48 ` Christoph Hellwig
2009-03-27 2:44 ` Anthony Liguori
2009-03-26 10:09 ` Avi Kivity
2009-03-26 18:19 ` Anthony Liguori
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=20090325181716.GA3215@infradead.org \
--to=hch@infradead.org \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
/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.