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: Thu, 26 Mar 2009 18:48:05 -0400 [thread overview]
Message-ID: <20090326224805.GA17658@infradead.org> (raw)
In-Reply-To: <49CB4633.5020208@redhat.com>
On Thu, Mar 26, 2009 at 11:09:07AM +0200, Avi Kivity wrote:
> If the repo contains only the kit (external-module.h and the hack
> scripts) we'll be left with dual repositories with their confusion and
> unbisectability. If the repo contains both the kit and the code, I'll
> need to commit every kvm.git change into that repository, which I'm sure
> to botch now and then.
>
> Do you see any specific problem with dropping kvm-userspace.git/kernel/*
> under kvm.git/scripts/kvm/?
Adding more stuff to a kernel tree that doesn't apply to building that
tree seems rather odd. But if it makes your life easier go for it, it's
defintively much better than the current setup.
next prev parent reply other threads:[~2009-03-26 22:48 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
2009-03-26 9:09 ` Avi Kivity
2009-03-26 22:48 ` Christoph Hellwig [this message]
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=20090326224805.GA17658@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.