Re: New SHA1 property for nodes returned 'svn ls --xml' invocations.

> > > As a test, I'm using openssl to make huge files that > > change wholly with every revision, and trying to find the top limits of > > Subversion. Sadly I've only found the top limits of Docker on the mac so > > far - 60GB. > > 60GB being the size of each revision of a single versioned file? >

Re: New SHA1 property for nodes returned 'svn ls --xml' invocations.

Paul Hammant wrote on Tue, Oct 11, 2016 at 20:14:02 -0400: > > > 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*

Re: New SHA1 property for nodes returned 'svn ls --xml' invocations.

> > Thanks for these details, they clarify the picture. > :) > > 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

Re: New SHA1 property for nodes returned 'svn ls --xml' invocations.

Paul Hammant wrote on Tue, Oct 11, 2016 at 08:09:06 -0400: > kind="file"> > 3bc64b30547e9a0448feba6c6af48447dff2b980 ⋮ > 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

Re: New SHA1 property for nodes returned 'svn ls --xml' invocations.

Personally and especially for my use case, I am not interested in the sha1 of properties. Others might be though. Therefore two sha1 hashes - one without props, and one with. Sent from my iPhone > On Oct 11, 2016, at 8:13 AM, Branko Čibej wrote: > >> On 11.10.2016 14:09,