From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JOm7D-0005zo-Pn for qemu-devel@nongnu.org; Mon, 11 Feb 2008 22:47:27 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JOm7D-0005zZ-2M for qemu-devel@nongnu.org; Mon, 11 Feb 2008 22:47:27 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JOm7C-0005zW-Tf for qemu-devel@nongnu.org; Mon, 11 Feb 2008 22:47:26 -0500 Received: from bsdimp.com ([199.45.160.85] helo=harmony.bsdimp.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JOm7C-0005Yw-GI for qemu-devel@nongnu.org; Mon, 11 Feb 2008 22:47:26 -0500 Date: Mon, 11 Feb 2008 20:46:02 -0700 (MST) Message-Id: <20080211.204602.920876733.imp@bsdimp.com> Subject: Re: [Qemu-devel] What does code_copy_enabled do? From: "M. Warner Losh" In-Reply-To: <200802120232.22591.paul@codesourcery.com> References: <200802081451.39008.rob@landley.net> <18352.28501.572044.730022@mariner.uk.xensource.com> <200802120232.22591.paul@codesourcery.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, paul@codesourcery.com Cc: Ian.Jackson@eu.citrix.com In message: <200802120232.22591.paul@codesourcery.com> Paul Brook 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