On 05.05.2014 06:56, David Balažic wrote:
> Ryan Schmidt wrote:
>> On May 4, 2014, at 15:46, David Balažic wrote:
>>
>>> Branko Čibej wandisco.com> writes:
>>>
It's not a question of SVN being fragile or not. The .svn/ directory
is private to Subversion and you're not allowed to fi
The ‘list’ command is really only implemented at a high level, by retrieving
the entries of each directory at a time and then filtering the results.
There is nothing you can do to really optimize this for directories without
changing the ra layer and wire protocol for svn:// and http://.
>
>
>
> The "depth" parameter is used in many places, not just in "svn list";
whatever enhancement you come up with must at least fit the other uses.
Depth was invented to describe sparse working copies, and was only later
adapted to other commands. For sparse working copies, "depth=dirs" probably
Ryan Schmidt wrote:
> On May 4, 2014, at 15:46, David Balažic wrote:
>
> > Branko Čibej wandisco.com> writes:
> >
> >>It's not a question of SVN being fragile or not. The .svn/ directory
> >>is private to Subversion and you're not allowed to fiddle with it.
> >
> > Servus Branko,
> >
>
Hi, Yonggang Luo,
I'm assuming you're using FSFS based repositories, as BDB repositories usually
won't suffer from this problem.
check the documentation about repository packing:
http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.diskspace.fsfspacking
Best regards
For really big repository, there is too much small files, that's hurt for
backup and checksums and copy/move operations.
--
此致
礼
罗勇刚
Yours
sincerely,
Yonggang Luo
