From: Roland Dreier <roland@topspin.com>
To: Arun Sharma <arun.sharma@intel.com>
Cc: Jim Greer <jbgreer@gmail.com>,
Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
Xen-devel@lists.xensource.com,
"Ronald G. Minnich" <rminnich@lanl.gov>,
Nicholas Lee <emptysands@gmail.com>
Subject: Re: Xen repository
Date: Wed, 25 May 2005 10:35:33 -0700 [thread overview]
Message-ID: <52acmjryxm.fsf@topspin.com> (raw)
In-Reply-To: <4294B55D.4000103@intel.com> (Arun Sharma's message of "Wed, 25 May 2005 10:26:53 -0700")
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.
next prev parent reply other threads:[~2005-05-25 17:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 7:47 Xen repository Ian Pratt
2005-05-23 8:27 ` aq
2005-05-23 15:17 ` Ronald G. Minnich
2005-05-23 13:06 ` Andrew Thompson
2005-05-23 16:38 ` Arun Sharma
2005-05-25 8:42 ` Nicholas Lee
2005-05-25 17:26 ` Arun Sharma
2005-05-25 17:35 ` Roland Dreier [this message]
2005-05-25 18:00 ` Ronald G. Minnich
2005-05-23 21:25 ` Jacob Gorm Hansen
-- strict thread matches above, loose matches on Subject: below --
2005-05-23 9:11 Ian Pratt
2005-05-24 19:21 ` Paul Larson
2005-05-24 19:55 ` Ronald G. Minnich
2005-05-21 20:16 Ian Pratt
2005-05-21 19:52 ` Mark Williamson
2005-05-22 1:00 ` Rik van Riel
2005-05-23 9:47 ` Vincent Hanquez
2005-05-22 2:42 ` aq
2005-05-23 3:34 ` Ronald G. Minnich
2005-05-21 16:28 Nakajima, Jun
2005-05-21 16:24 Jim Greer
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=52acmjryxm.fsf@topspin.com \
--to=roland@topspin.com \
--cc=Xen-devel@lists.xensource.com \
--cc=arun.sharma@intel.com \
--cc=emptysands@gmail.com \
--cc=jbgreer@gmail.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=rminnich@lanl.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.