public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: kvm repository unification
Date: Tue, 20 Mar 2007 14:13:11 +0200	[thread overview]
Message-ID: <45FFCFD7.5000107@qumranet.com> (raw)

Managing userspace in subversion and the kernel in git is proving to be 
quite a pain.  Branches have to be maintained in parallel, tagging is 
awkward, and bisection is fairly impossible.

What do people think about putting libkvm and qemu into the usr 
directory of the kernel repo?  It's slightly wierd but will make life 
generally easier.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

             reply	other threads:[~2007-03-20 12:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-20 12:13 Avi Kivity [this message]
     [not found] ` <45FFCFD7.5000107-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-20 12:21   ` kvm repository unification Gregory Haskins
     [not found]     ` <45FF8B73.BA47.005A.0-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
2007-03-20 12:37       ` Avi Kivity
     [not found]         ` <45FFD598.2050403-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-20 12:58           ` Gregory Haskins
     [not found]             ` <45FF9418.BA47.005A.0-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
2007-03-20 13:02               ` Avi Kivity
     [not found]                 ` <45FFDB50.7050105-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-20 13:10                   ` Gregory Haskins
2007-03-20 13:20   ` Arnd Bergmann
     [not found]     ` <200703201420.10139.arnd-r2nGTMty4D4@public.gmane.org>
2007-03-20 13:40       ` Dor Laor
2007-03-20 13:46       ` Avi Kivity
     [not found]         ` <45FFE5AB.3030501-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-20 14:10           ` Anthony Liguori
     [not found]             ` <45FFEB6B.4090301-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-03-20 14:38               ` Avi Kivity
2007-03-20 14:37           ` Arnd Bergmann
     [not found]             ` <200703201537.35704.arnd-r2nGTMty4D4@public.gmane.org>
2007-03-20 14:43               ` Avi Kivity
     [not found]                 ` <45FFF312.2030804-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-20 15:58                   ` Anthony Liguori
     [not found]                     ` <4600049C.7090905-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-03-20 16:03                       ` Avi Kivity
     [not found]                         ` <460005CE.4080406-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-20 19:36                           ` Arnd Bergmann
     [not found]                             ` <200703202036.33702.arnd-r2nGTMty4D4@public.gmane.org>
2007-03-21 12:49                               ` Avi Kivity
2007-03-21 19:59   ` David Beal

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=45FFCFD7.5000107@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox