From: Anthony Liguori <anthony@codemonkey.ws>
To: Christoph Hellwig <hch@infradead.org>
Cc: Avi Kivity <avi@redhat.com>, KVM list <kvm@vger.kernel.org>
Subject: Re: Split kvm source tarballs
Date: Thu, 26 Mar 2009 21:44:01 -0500 [thread overview]
Message-ID: <49CC3D71.4050709@codemonkey.ws> (raw)
In-Reply-To: <20090326224859.GB17658@infradead.org>
Christoph Hellwig wrote:
> On Thu, Mar 26, 2009 at 01:19:46PM -0500, Anthony Liguori wrote:
>
>>> Slightly offtopic, but I always wondered why qemu is hosted in svn. For
>>> all project having semi-forks of qemu that they try to keep in sync
>>> or even merge back a distributed scm would work so much better.
>>>
>>>
>> I'm going to switch it to git fwiw.
>>
>
> If it's soon enough maybe the kvm repository reorganization should wait
> for it so that the new repository can be cloned from upstream qemu?
>
It'll be compatible with the kernel.org git tree so there's no need to wait.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-03-27 2:44 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
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 [this message]
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=49CC3D71.4050709@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=hch@infradead.org \
--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 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).