|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-devel
Re: [Xen-devel] Xen repository
 
| 
To:  | 
Arun Sharma <arun.sharma@xxxxxxxxx> | 
 
| 
Subject:  | 
Re: [Xen-devel] Xen repository | 
 
| 
From:  | 
Roland Dreier <roland@xxxxxxxxxxx> | 
 
| 
Date:  | 
Wed, 25 May 2005 10:35:33 -0700 | 
 
| 
Cc:  | 
Jim Greer <jbgreer@xxxxxxxxx>, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>,	Xen-devel@xxxxxxxxxxxxxxxxxxx, "Ronald G. Minnich" <rminnich@xxxxxxxx>,	Nicholas Lee <emptysands@xxxxxxxxx> | 
 
| 
Delivery-date:  | 
Wed, 25 May 2005 17:35:01 +0000 | 
 
| 
Envelope-to:  | 
www-data@xxxxxxxxxxxxxxxxxxx | 
 
| 
In-reply-to:  | 
<4294B55D.4000103@xxxxxxxxx> (Arun Sharma's message of "Wed, 25	May 2005 10:26:53 -0700") | 
 
| 
List-help:  | 
<mailto:xen-devel-request@lists.xensource.com?subject=help> | 
 
| 
List-id:  | 
Xen developer discussion <xen-devel.lists.xensource.com> | 
 
| 
List-post:  | 
<mailto:xen-devel@lists.xensource.com> | 
 
| 
List-subscribe:  | 
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe> | 
 
| 
List-unsubscribe:  | 
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> | 
 
| 
References:  | 
<A95E2296287EAD4EB592B5DEEFCE0E9D1E4173@xxxxxxxxxxxxxxxxxxxxxxxxxxx>	<20050523163831.GB5916@xxxxxxxxxxxxxxx>	<2b6116b30505250142128e5514@xxxxxxxxxxxxxx>	<4294B55D.4000103@xxxxxxxxx> | 
 
| 
Sender:  | 
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx | 
 
| 
User-agent:  | 
Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, linux) | 
 
 
 
    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.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 |   
 
 | 
    | 
  
  
    |   | 
    |