public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: Randy Thelen <Randy.Thelen-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Getting consistent source trees
Date: Tue, 20 Mar 2007 20:33:03 -0500	[thread overview]
Message-ID: <46008B4F.6030407@codemonkey.ws> (raw)
In-Reply-To: <7F4E2EA8-4B25-453F-AABA-1CD2ED4C9905-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>

Randy Thelen wrote:
> Folks --
>
> The instructions on getting a source tree, e.g., kvm-17 is a bit  
> convoluted.  I know that you'd like to simplify the process from a  
> development standpoint (i.e., the unification mail the last couple of  
> days discusses this).  But, could I encourage you to document the  
> process of getting a kvm numbered tree in a wee-bit more detail over  
> on the "code" page of the wiki?
>
> For example, we grabbed source bits out of kvm/public/17.  But then  
> mashing those with other source bits felt more complicated than  
> necessary.
>   

I don't think it is all that avoidable as KVM becomes more intertwined 
with the kernel.  Certainly, when/if a syscall interface is introduced, 
the ability to be an external module will go away entirely.  Hopefully, 
in the near future, you won't need to have such a close link between 
kernel version/userspace such that they can be treated more or less as 
two separate projects.

If KVM ever does something like a sparse tree, I think I'm going to go 
live in a cave somewhere.

Regards,

Anthony Liguori

> -- Randy
>
> -------------------------------------------------------------------------
> 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
> _______________________________________________
> kvm-devel mailing list
> kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
>   


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

  parent reply	other threads:[~2007-03-21  1:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21  1:27 Getting consistent source trees Randy Thelen
     [not found] ` <7F4E2EA8-4B25-453F-AABA-1CD2ED4C9905-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>
2007-03-21  1:33   ` Anthony Liguori [this message]
2007-03-21  7:07   ` 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=46008B4F.6030407@codemonkey.ws \
    --to=anthony-rdkfgonbjusknkdkm+me6a@public.gmane.org \
    --cc=Randy.Thelen-HgOvQuBEEgTQT0dZR+AlfA@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