svnadmin lslocks ambiguity
From: Trent Fisher <trent.fisher_at_oracle.com>
Date: Mon, 6 Jan 2020 13:22:24 -0500
I just noticed something odd about "svnadmin lslocks"... perhaps a bug?
The (short version) backstory is that I am trying to clear all locks
The svnadmin lslocks command listed no locks, but if I specified the
$ svnadmin lslocks /scm/svn/repos/hhhh
$ svnadmin lslocks /scm/svn/repos/hhhh '/some/file/omitted.foo'
This seems like a bug in lslocks, why would it not list *all* the locks?
This is SVN 1.10.4 on Linux
This is an archived mail posted to the Subversion Users mailing list.