From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Juanma Barranquero" Newsgroups: gmane.emacs.devel Subject: Re: Switching to Subversion Date: Mon, 13 Nov 2006 00:37:51 +0100 Message-ID: References: <87bqne87ur.fsf@catnip.gol.com> <10609.1163264429@olgas.newt.com> <87fycphhyr.fsf@pacem.orebokech.com> <87odrdzci9.fsf@olgas.newt.com> <87ac2w45e0.fsf@catnip.gol.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1163374693 28978 80.91.229.2 (12 Nov 2006 23:38:13 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 12 Nov 2006 23:38:13 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 13 00:38:08 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GjOtr-0008Ny-E8 for ged-emacs-devel@m.gmane.org; Mon, 13 Nov 2006 00:38:07 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GjOtq-0002a5-RE for ged-emacs-devel@m.gmane.org; Sun, 12 Nov 2006 18:38:06 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GjOte-0002Zq-Ko for emacs-devel@gnu.org; Sun, 12 Nov 2006 18:37:54 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GjOtd-0002ZU-5O for emacs-devel@gnu.org; Sun, 12 Nov 2006 18:37:54 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GjOtd-0002ZP-0f for emacs-devel@gnu.org; Sun, 12 Nov 2006 18:37:53 -0500 Original-Received: from [64.233.162.193] (helo=nz-out-0102.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GjOtd-00048V-2D for emacs-devel@gnu.org; Sun, 12 Nov 2006 18:37:53 -0500 Original-Received: by nz-out-0102.google.com with SMTP id r28so627307nza for ; Sun, 12 Nov 2006 15:37:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=C9qBgWImZEAt+hK4qSdFzdU13GhmEah3eldj0Tk2OALoqe732l1mRroKwDQVi+z6ErgVghTQnuf1L2pIsrQ+a/CQXFG3Wf0EGM0YDZvNOQ1A8c04iddGPWnNabA3A3mas0dw2Mwa7+tETnXS12R2ar5DTBGR+scemPmkyrXh5oI= Original-Received: by 10.35.79.3 with SMTP id g3mr370410pyl.1163374671999; Sun, 12 Nov 2006 15:37:51 -0800 (PST) Original-Received: by 10.35.95.18 with HTTP; Sun, 12 Nov 2006 15:37:51 -0800 (PST) Original-To: "Miles Bader" In-Reply-To: <87ac2w45e0.fsf@catnip.gol.com> Content-Disposition: inline X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:62154 Archived-At: On 11/13/06, Miles Bader wrote: > He provides pretty good arguments _against_ subversion Based on false statements, like this one: "The old Berkeley DB-based backend has been deprecated as unstable and subject to corruption [..." FSFS is the default, but the BDB backend was never "deprecated as unstable". And, in the ChangeLog of the latest release, there's this bit of information: A common problem with previous versions of Subversion is that crashed server processes could leave BerkeleyDB-based repositories in an unusable "wedged" state, requiring administrators to manually intervene and bring back online. (Note: this is not due to bugs in BerkeleyDB, but due to the unorthodox way in which Subversion uses it!) Subversion 1.4 can now be compiled against BerkeleyDB 4.4, which has a new "auto-recovery" feature. If a Subversion server process crashes and leaves the repository in an inconsistent state, the next process which attempts to access the repository will notice the problem, grab exclusive control of the repository, and automatically recover it. In theory (and in our testing), this new feature makes BerkeleyDB-based repositories just as wedge-proof as FSFS repositories. > And yes, Havoc, anyone seriously entertaining moving to SVN should have > their heads examined. Ah, yes, a good technical argument. /L/e/k/t/u