Re: Corrupt log message in repository

On Mon, Mar 01, 2004 at 12:25:24AM -0800, Garrick Olson wrote:
> This still seems like an svn bug to me. Shouldn't the *server* enforce
> any of these kinds of conventions a client must follow?
>
> As a repository owner, it is difficult for me to control what clients
> are being used, and I would expect the server to prevent repository
> corruption even by potentially adversarial clients.

It'd be nice if that was the case but that doesn't help us now. We've
got a released product.

However, in the future I don't see any reason this couldn't be dealt
with. The question is, would erroring out on this be a change in an
implementation detail or an actual change of our API that we'd have to
make a new function call for or wait for 2.0 to make.

I'm not sure. I can see both arguments. On one hand our documentation
says you're supposed to do this conversion already so us erroring out
wouldn't be necessarily unexpected, provided we can do so with an
existing error message that makes sense.

But on the other hand it's not behavior that we're exhibiting now.

-- 
Ben Reser <ben@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org