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

Re: Lock non-existent to allow reserving a path

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Mon, 24 Feb 2014 14:00:11 -0500

On 02/24/2014 01:56 PM, Philip Martin wrote:
> Thomas Ã…kesson <thomas.akesson_at_simonsoft.se> writes:
>> Svn does not allow locking non-existent paths. It is blocked both in
>> libsvn_fs_base/libsvn_fs_fs as well as in mod_dav_svn. In the same
>> areas of the code in fs comments say:
>> "While our locking implementation easily supports the locking of
>> nonexistent paths, we deliberately choose not to allow such madness."
>> Given that we now present valid use-cases, it is reassuring that the
>> authors of the locking code said it "easily supports the locking of
>> nonexistent paths".
> There is a way to create such locks at present: checkout, lock a file,
> delete the file or parent directory, commit with --no-unlock. We have a
> regression test for this: lock_tests.py:deleted_path_lock. (Possibly
> this behaviour could be considered a bug, perhaps 'commit --no-unlock'
> should remove the locks on deleted files, but implementing that would be
> hard.)

That behavior *is* a bug that someone must have decided post-facto might
be useful. But hey, I'm not pointing fingers. That approach has
brought us such awesome features in the past as "file externals".


Received on 2014-02-24 20:00:47 CET

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

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