On 5/5/06, Christian Bang <cbang@gmx.net> wrote:
> Hello,
>
> I get the above error every time the first commit crashes for some
> reason and I try to commit again. Some files are now in the repository
> but still scheduled for addition in the local copy. (A clean doesn't
> cancel these additions.) An update of the repository doesn't help since
> no other user accessed the repository in the meanwhile.
> I thought, it could never happen that some files of one commit are added
> while others aren't since in case of an error the transaction is rolled
> back?!
It can't happen. Well, you can't get "some of the files" into the
repository without all of them being committed. You can get "all of
the files" into the repository but not have your working copy be
updated to reflect that fact. The commit is atomic, but the updating
of the working copy afterwards is not.
I suspect you're missinterpreting the error message, or your
description of the problem is a bit off.
Unfortunately, without a reproduction recipie, or at the very least
the actual error message you're seeing, it's hard to tell for sure one
way or the other.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 8 23:15:48 2006