From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@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: Wed, 21 Mar 2007 09:07:38 +0200 [thread overview]
Message-ID: <4600D9BA.200@qumranet.com> (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'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
prev parent reply other threads:[~2007-03-21 7:07 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
2007-03-21 7:07 ` Avi Kivity [this message]
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=4600D9BA.200@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@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