My understanding was that they claimed all updates to the repository were atomic, not that they claim all updates to your local filesystem are atomic. In other words, the update to the repo should have either succeeded or failed all together, but a large checkout or merge may fail and whack your local tree. Certainly I've seen some weird behavior where I had to delete a local directory and check it out again due to svn being confused.
Aaron On Thu, 2 Dec 2004, Alan D. Cabrera wrote: > That is subversion's claim, that all changes are atomic. > > > Regards, > Alan > > -----Original Message----- > From: David Jencks [mailto:[EMAIL PROTECTED] > Sent: Thu 12/2/2004 8:58 PM > To: [EMAIL PROTECTED] > Cc: > Subject: subversion peculiar behaviour? > > > > On the jetty-deployer branch I tried to check in a large change, > Aaron's move of service-builder etc. I ended up with an timeout error > and no commit email seems to have appeared, but it looks like at least > part of the changes are committed. Can I be certain that the entire > commit happened atomically? > > thanks > david jencks > > > >
