<html><head></head><body>I must have missed all those other threads. I'm curious about a use case where there is no perceived value to having atomic multi-file commits. <div class="gmail_quote">Chris Hecker <checker@d6.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <pre class="k9mail"> Can we please stop the CVS threads? bzr is having enough issues recently without the mailing list turning into a giant redundant flame war. Chris On 2013-09-09 13:07, Mark A. Flacy wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">On Monday, September 09, 2013 09:13:35 AM Thorsten Glaser wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">On Fri, 6 Sep 2013, JP Vossen wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">have to disagree there. CVS is fundamentally broken because of the </blockquote></blockquote>way it <blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">does everything "per file."</blockquote> For a *lot* of workloads, this is better than the models used by svn, bzr or *shudder* git.</blockquote> Those would be workloads where each file that you have under version control is totally unrelated to every other file that is being version controlled. Otherwise, you'd be mildly interested in the ability to make atomic changes to more than one file at once. I'm mildly interested in an example of one of these workloads. -- Mark A. Flacy</blockquote> </pre></blockquote></div> -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.</body></html>