Description
In a nutshell, you can lock a file, then delete the file, but retain the lock. This is in effect a denial-of-service because then the file can never be created again, even by the user holding the lock on the now-obsolete file. Some on IRC said this can be a useful feature. If it is decided the functionality should be kept, I feel the errors being returned need to indicate in a better manner what is actually failing. Specific test case and peer-review at http://colabti.de/irclogger/irclogger_log/svn?date=2007-10-17,Wed;raw=on around 21:00. Search for "RevRag" because I misspelled the name on the paste page ( http://paste.lisp.org/display/49343 ). If you do "svn cat" on the locked file, you get error 404 (but if the file doesn't exist at all, you get "path not found").
http://colabti.de/irclogger/irclogger_log/svn?date=2007-10-17,Wed;raw=on
Original issue reported by revragnarok
Attachments
Issue Links
- duplicates
-
SVN-2507 'commit --no-unlock' doesn't remove locks on files deleted
- Open