From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Getting consistent source trees Date: Wed, 21 Mar 2007 09:07:38 +0200 Message-ID: <4600D9BA.200@qumranet.com> References: <7F4E2EA8-4B25-453F-AABA-1CD2ED4C9905@netapp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Randy Thelen Return-path: In-reply-to: <7F4E2EA8-4B25-453F-AABA-1CD2ED4C9905-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org> 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 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