* Getting consistent source trees
@ 2007-03-21 1:27 Randy Thelen
[not found] ` <7F4E2EA8-4B25-453F-AABA-1CD2ED4C9905-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>
0 siblings, 1 reply; 3+ messages in thread
From: Randy Thelen @ 2007-03-21 1:27 UTC (permalink / raw)
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
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.
-- 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Getting consistent source trees
[not found] ` <7F4E2EA8-4B25-453F-AABA-1CD2ED4C9905-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>
@ 2007-03-21 1:33 ` Anthony Liguori
2007-03-21 7:07 ` Avi Kivity
1 sibling, 0 replies; 3+ messages in thread
From: Anthony Liguori @ 2007-03-21 1:33 UTC (permalink / raw)
To: Randy Thelen; +Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Getting consistent source trees
[not found] ` <7F4E2EA8-4B25-453F-AABA-1CD2ED4C9905-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>
2007-03-21 1:33 ` Anthony Liguori
@ 2007-03-21 7:07 ` Avi Kivity
1 sibling, 0 replies; 3+ messages in thread
From: Avi Kivity @ 2007-03-21 7:07 UTC (permalink / raw)
To: Randy Thelen; +Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
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've updated the page to mention the tagging scheme used.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-03-21 7:07 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2007-03-21 7:07 ` Avi Kivity
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox