From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: kvm repository unification Date: Tue, 20 Mar 2007 14:20:09 +0100 Message-ID: <200703201420.10139.arnd@arndb.de> References: <45FFCFD7.5000107@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Return-path: In-Reply-To: <45FFCFD7.5000107-atKUWr5tajBWk0Htik3J/w@public.gmane.org> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org On Tuesday 20 March 2007, Avi Kivity wrote: > Managing userspace in subversion and the kernel in git is proving to be = > quite a pain. =A0Branches 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? =A0It's slightly wierd but will make life = > generally easier. In my projects, I tend to never have a complete kernel tree under revision control, only patches in a form suitable for 'quilt mail'. This makes it a lot easier to see how the patches will look when they get merged upstream. If you like, I can give you a copy of the scripts that I use to maintain the quilt tree I maintain for the cell kernel. Arnd <>< ------------------------------------------------------------------------- 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=3Djoin.php&p=3Dsourceforge&CID=3DDE= VDEV