[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Locks return 'Bad Request'

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Wed, 27 Feb 2008 17:08:26 -0500

"Joel Low" <joel_at_joelsplace.sg> writes:
> I wrote one; sorry for not making clear. Attached patch from trunk.

Thanks! (See my other mail just now about apr_pcalloc...)

> Index: lock.c
> ===================================================================
> --- lock.c (revision 29593)
> +++ lock.c (working copy)
> @@ -390,6 +390,7 @@
> "Failed to generate a lock token.",
> resource->pool);
> dlock->locktoken = token;
> + dlock->next = NULL;
>
> /* allowing mod_dav to fill in dlock->timeout, owner, auth_user. */
> /* dlock->info and dlock->next are NULL by default. */

This should be a no-op, since that memory is already zero. Are you
saying this fixes a bug in trunk for you??

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-27 23:08:51 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.