Paul Hammant wrote on Tue, Oct 11, 2016 at 08:09:06 -0400:
> <entry
> kind="file">
> <content-sha1>3bc64b30547e9a0448feba6c6af48447dff2b980<content-sha1>
⋮
> For the entry of directory that contains mod_dav_svn.c, I'd hope for the
> SHA1 to be a function of the SHA1s of the files within.
⋮
> For my use-case to work, I need to have a reasonable chance of
> recalculating the SHA1 on the client file system without access to the
> remote repo, or the presence of a .svn directory.
Thanks for these details, they clarify the picture.
> I don't have an opinion about symlinks, of experience of them with Svn. I'm
> unfamilar with the hat-syntax wc-centric use of svn-ls. Therefore I don't
> know what to say about it.
^/foo is shorthand for the URL "${REPOS_ROOT_URL}/foo". I used that
colloquially; didn't mean to imply existence of a wc.
> I've read the ?kw=1 section of the release notes. My use case would not
> need keyword replacement. In fact it would need it to be off.
>
Are you sure? The only situations in which you'd need keywords
expansion *off* is if your files *do* have svn:keywords set, but you
used neither 'svn export' nor 'svn checkout' to extract the tree in the
first place.
> Something about something Greek in
> https://svn.apache.org/repos/asf/subversion/tree/readme ? - I'm lost and
> need further guidance as to reading materials, please.
>
I gave you the wrong filename earlier, sorry; the correct one is
https://svn.apache.org/repos/asf/subversion/trunk/subversion/tests/greek-tree.txt
But it's not important; your examples with subversion/mod_dav_svn/ sufficed.
Daniel
