Re: svn commit: r12264 - in branches/locking/subversion: include libsvn_client libsvn_fs libsvn_fs_base libsvn_fs_fs libsvn_ra_dav libsvn_ra_local libsvn_ra_svn libsvn_repos mod_dav_svn svnadmin svnserve

On Thu, 9 Dec 2004 [email protected] wrote:

> Author: sussman
> Date: Thu Dec  9 14:00:28 2004
> New Revision: 12264
>
> Modified: branches/locking/subversion/include/svn_fs.h
> Url: http://svn.collab.net/viewcvs/svn/branches/locking/subversion/include/svn_fs.h?view=diff&rev=12264&p1=branches/locking/subversion/include/svn_fs.h&r1=12263&p2=branches/locking/subversion/include/svn_fs.h&r2=12264
> ==============================================================================
> --- branches/locking/subversion/include/svn_fs.h	(original)
> +++ branches/locking/subversion/include/svn_fs.h	Thu Dec  9 14:00:28 2004
> @@ -1498,6 +1498,10 @@
>   * If @a timeout is zero, then create a non-expiring lock.  Else, the
>   * lock will expire in @a timeout seconds after creation.
>   *
> + * If @a current_rev is a valid revnum, then do an out-of-dateness
> + * check.  If the revnum is less than the last-changed-revision of @a
> + * path, return SVN_ERR_FS_OUT_OF_DATE.
> + *

As I understand the spec, a client can add a file and lock it, to
"reserve" the pathname. Then, the server needs to do out-of-dateness
checking meaning that the file shouldn't be in HEAD. What do I pass in
this case? Maybe it is celar from the code, but the docstring doesn't say
what happens to a non-existent file.

//Peter