Re: kvm repository unification

[Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>]

Anthony Liguori wrote:
>>  
>
> I think a single repository with libkvm and a QEMU and kernel patch 
> queue (quilt or mq, it doesn't matter to me) would be best.
>
> Patches in the main queue would get folded upstream quickly 
> (hopefully).  Devs would submit new patches that you may choose to 
> either add to the queue or fold an existing patch.
>
> I actually find that it's easier to do merging with a patch queue than 
> by directly committing.
>

One issue I see with it is that it's impossible to go back in history, 
as the reference point to which patches are applied changes in time.  
Perhaps I could record the nearest git tag in a version controlled file, 
and the build scripts would checkout that tag from an associated kernel 
git repo.


-- 
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