Malcolm Rowe wrote:
> ...
>
> Disk: 1=================
> Mem: ...
>
> For whatever reason, we don't abort the transaction, but instead write
> out the file's contents again. This succeeds, so now we have this:
>
> Disk: 1=================2########################>
> Mem: ...
>
> ...
>
> It's not currently planned for a release, since we're not entirely sure
> how best to fix it. There's a couple of approaches:
>
> ...
Why isn't it the only valid behaviour that the transaction is cancelled
if there is a disk write error?
Otherwise the repository contains broken file content.
Cheers,
Folker
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 8 16:19:22 2006