From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roland Dreier Subject: Re: Xen repository Date: Wed, 25 May 2005 10:35:33 -0700 Message-ID: <52acmjryxm.fsf@topspin.com> References: <20050523163831.GB5916@sharma-home.net> <2b6116b30505250142128e5514@mail.gmail.com> <4294B55D.4000103@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: <4294B55D.4000103@intel.com> (Arun Sharma's message of "Wed, 25 May 2005 10:26:53 -0700") List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Arun Sharma Cc: Jim Greer , Ian Pratt , Xen-devel@lists.xensource.com, "Ronald G. Minnich" , Nicholas Lee List-Id: xen-devel@lists.xenproject.org Arun> Why would a read-mostly user need atomic commits? For Arun> changesets, something like mercurial would give more Arun> information, because it's able to represent branches and Arun> merges better. Atomic commits are extremely useful for read-mostly users -- with per-file versioning as in CVS, it becomes very difficult to do a binary search to find out which changeset introduced a problem. With subversion, it's quite easy for a tester to do this and be able to say "r1234 worked for me, r1235 crashes." - R.