From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, paul@codesourcery.com
Cc: Ian.Jackson@eu.citrix.com
Subject: Re: [Qemu-devel] What does code_copy_enabled do?
Date: Mon, 11 Feb 2008 20:46:02 -0700 (MST) [thread overview]
Message-ID: <20080211.204602.920876733.imp@bsdimp.com> (raw)
In-Reply-To: <200802120232.22591.paul@codesourcery.com>
In message: <200802120232.22591.paul@codesourcery.com>
Paul Brook <paul@codesourcery.com> writes:
: > > 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.
: While I can see that distributed revision control systems do enable some
: interesting possibilities, there's certainly no clear winner. All of them
: seem to have have fairly serious issues with either usability, portability,
: scalability, and/or require learning a whole new workflow. I'm sure
: advocates of each system will claim that their system is the "best", but I
: remain unconvinced.
Well, svn now has svn to hg and svn to git gateways, so really it
caters to all comers...
Warner
next prev parent reply other threads:[~2008-02-12 3:47 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 [this message]
2008-02-12 11:30 ` Julian Seward
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=20080211.204602.920876733.imp@bsdimp.com \
--to=imp@bsdimp.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).