All of lore.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <muli-7z/5BgaJwgfQT0dZR+AlfA@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Version control system for KVM?
Date: Tue, 14 Nov 2006 18:43:22 +0200	[thread overview]
Message-ID: <20061114164322.GC6848@rhun.ibm.com> (raw)
In-Reply-To: <4559F0E9.1050503-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

On Tue, Nov 14, 2006 at 06:38:01PM +0200, Avi Kivity wrote:

> subversion on sourceforge

Eeek on both accounts... I strongly recommend git or mercurial at
least for the kernel bits. Also, if svn on sf is as bad as CVS used to
be there... you're in for a lot of pain.

Cheers,
Muli

-------------------------------------------------------------------------
SF.net email is sponsored by: A Better Job is Waiting for You - Find it Now.
Check out Slashdot's new job board. Browse through tons of technical jobs
posted by companies looking to hire people just like you.
http://jobs.slashdot.org/

  parent reply	other threads:[~2006-11-14 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14 14:02 Version control system for KVM? Simon Kagstrom
     [not found] ` <87u01286uc.wl%simon.kagstrom-6Uc+yI3S9P8@public.gmane.org>
2006-11-14 15:51   ` Avi Kivity
     [not found]     ` <4559E604.9090909-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-11-14 16:36       ` Muli Ben-Yehuda
     [not found]         ` <20061114163651.GB6848-k73YwwB0fHlWk0Htik3J/w@public.gmane.org>
2006-11-14 16:38           ` Avi Kivity
     [not found]             ` <4559F0E9.1050503-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-11-14 16:43               ` Muli Ben-Yehuda [this message]
     [not found]                 ` <20061114164322.GC6848-k73YwwB0fHlWk0Htik3J/w@public.gmane.org>
2006-11-14 16:48                   ` 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=20061114164322.GC6848@rhun.ibm.com \
    --to=muli-7z/5bgajwgfqt0dzr+alfa@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.