From: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: userspace repositories
Date: Thu, 25 Oct 2007 13:37:27 -0500 [thread overview]
Message-ID: <1193337447.28279.27.camel@basalt> (raw)
In-Reply-To: <4720DC70.6090607-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Avi, what do you think about breaking the kvm-userspace repository into
separate kvm-qemu, kvmctl, and libkvm repositories?
--
Hollis Blanchard
IBM Linux Technology Center
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-25 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 3:26 [PATCH 0 of 2] [v2] Another attempt to Consolidate x86 makefiles & tests jyoung5-r/Jw6+rmf7HQT0dZR+AlfA
2007-10-24 3:26 ` [PATCH 1 of 2] consolidate x86 user makefiles jyoung5-r/Jw6+rmf7HQT0dZR+AlfA
2007-10-24 14:32 ` [kvm-ppc-devel] " Hollis Blanchard
2007-10-24 3:26 ` [PATCH 2 of 2] Move all x86 specific tests to there own directory jyoung5-r/Jw6+rmf7HQT0dZR+AlfA
2007-10-24 14:32 ` [kvm-ppc-devel] " Hollis Blanchard
2007-10-25 18:12 ` [PATCH 0 of 2] [v2] Another attempt to Consolidate x86 makefiles & tests Avi Kivity
[not found] ` <4720DC70.6090607-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-25 18:37 ` Hollis Blanchard [this message]
2007-10-25 18:40 ` userspace repositories Avi Kivity
[not found] ` <4720E312.3060400-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-25 19:01 ` Hollis Blanchard
2007-10-25 19:03 ` Avi Kivity
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=1193337447.28279.27.camel@basalt \
--to=hollisb-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.