Daniel Shahaf <[email protected]> writes:
> 1. 'svn lock ^/trunk/iota' creates an md5("/trunk") digest file. That
> digest file is not referenced by the md5("/") digest file; both of
> these digest files refer only and directly to the md5("/trunk/iota")
> digest file.
>
> Does the md5("/trunk") digest file have to be preserved in a hotcopy?
> Given that it is unreferenced, under what conditions would it be read
> --- when the reader is pre-1.7?
Yes, it's used by operations on /trunk:
$ svnadmin create repo
$ svn import -mm Makefile file://`pwd`/repo/trunk/f
$ svn lock file://`pwd`/repo/trunk/f
$ svn rm -mm file://`pwd`/repo/trunk
svn: Cannot verify lock on path '/trunk/f'; no matching lock-token available
$ rm -f repo/db/locks/9fd/9fdfca3f0419c7cff7f2d1f623525d29
$ svn info file://`pwd`/repo/trunk/f | grep Owner
Lock Owner: pm
$ svn rm -mm file://`pwd`/repo/A
Committed revision 2.
So deleting md5("/trunk") meant that the lock no longer stopped the
commit.
--
Philip
