From: Julian Seward <jseward@acm.org>
To: qemu-devel@nongnu.org
Cc: Ian.Jackson@eu.citrix.com, paul@codesourcery.com
Subject: Re: [Qemu-devel] What does code_copy_enabled do?
Date: Tue, 12 Feb 2008 12:30:53 +0100 [thread overview]
Message-ID: <200802121230.53157.jseward@acm.org> (raw)
In-Reply-To: <20080211.204602.920876733.imp@bsdimp.com>
> : > > Any news on the possible cvs->svn migration?
> : >
> : > To be perfectly honest, IMO there is little point moving an existing
> : > project from CVS to SVN.
> :
> : I disagree. CVS has several fairly fundamental flaws (no global revision
> : IDs, unable to move files, and more subtle problems with branches/tags).
> : SVN fixes these, and in most cases works as a direct drop-in replacement
> : for CVS.
>
> FreeBSD is moving from CVS to SVN for these reasons.
Just to second "M. Warner Losh": we moved Valgrind from CVS to SVN about
3.5 years ago and it was an excellent thing to do. It is not true to say
there is no advantage over CVS -- the global revision IDs, the ability to
rename files, and a simpler branching/tagging model are all big advantages.
And the fact that it is more-or-less conceptually a drop-in replacement makes
it easy for people to make the migration.
Sure, Valgrind is a tiny project compared to FreeBSD. But we gain those
advantages nonetheless.
J
next prev parent reply other threads:[~2008-02-12 11:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 6:48 Git/SVN/CVS? was Re: [Qemu-devel] What does code_copy_enabled do? Blue Swirl
2008-02-09 12:45 ` Johannes Schindelin
2008-02-09 14:10 ` Blue Swirl
2008-02-09 14:22 ` Johannes Schindelin
2008-02-09 15:20 ` Felipe Contreras
2008-02-09 16:49 ` Johannes Schindelin
2008-02-08 2:42 ` Rob Landley
2008-02-08 3:52 ` Paul Brook
2008-02-08 20:51 ` Rob Landley
2008-02-11 15:50 ` Ian Jackson
2008-02-11 16:10 ` Johannes Schindelin
2008-02-11 16:12 ` Ian Jackson
2008-02-11 15:52 ` Ian Jackson
2008-02-11 19:30 ` Felipe Contreras
2008-02-11 20:38 ` Johannes Schindelin
2008-02-11 21:19 ` Rob Landley
2008-02-11 21:19 ` Felipe Contreras
2008-02-12 2:32 ` Paul Brook
2008-02-12 3:46 ` M. Warner Losh
2008-02-12 11:30 ` Julian Seward [this message]
2008-02-12 11:15 ` Johannes Schindelin
2008-02-12 12:06 ` Andreas Färber
2008-02-12 11:57 ` Ian Jackson
2008-02-12 12:51 ` Johannes Schindelin
2008-02-12 12:59 ` Ian Jackson
2008-02-12 13:37 ` Johannes Schindelin
2008-02-12 13:52 ` Ian Jackson
2008-02-13 8:22 ` Rob Landley
2008-02-13 9:18 ` Felipe Contreras
2008-02-11 21:00 ` Git/SVN/CVS? was " Rob Landley
2008-02-11 21:28 ` Johannes Schindelin
2008-02-12 2:34 ` Rob Landley
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=200802121230.53157.jseward@acm.org \
--to=jseward@acm.org \
--cc=Ian.Jackson@eu.citrix.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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.