> -----Original Message-----
> From: Johan Corveleyn [mailto:jcor...@gmail.com]
> Sent: dinsdag 23 september 2014 10:04
> To: Elias Wulcan
> Cc: users@subversion.apache.org
> Subject: Re: log-report with conflicting revision range and limit
>
> On Tue, Sep 23, 2014 at 9:35 AM, Elias Wulcan <elias.wul...@apptus.com>
> wrote:
> > Hello,
> >
> >
> >
> > I’m trying to figure out why a client is extremely slow fetching subversion
> > history. Here’s an excerpt from its TCP traffic with the repository.
> >
> >
> >
> > REPORT /products/ecom/!svn/bc/16411/x/branches/z HTTP/1.1
> >
> > Host: a.b.local
> >
> > Authorization: Basic XXXXXXXXX
> >
> > User-Agent: SVN/1.8.10 (x64-microsoft-windows) serf/1.3.7
> >
> > Content-Type: text/xml
> >
> > Accept-Encoding: gzip
> >
> > DAV: http://subversion.tigris.org/xmlns/dav/svn/depth
> >
> > DAV: http://subversion.tigris.org/xmlns/dav/svn/mergeinfo
> >
> > DAV: http://subversion.tigris.org/xmlns/dav/svn/log-revprops
> >
> > Transfer-Encoding: chunked
> >
> >
> >
> > 151
> >
> > <S:log-report
> > xmlns:S="svn:"><S:start-revision>16411</S:start-revision><S:end-
> revision>1</S:end-revision><S:limit>12</S:limit><S:discover-changed-
> paths></S:discover-changed-paths><S:include-merged-
> revisions></S:include-merged-
> revisions><S:revprop>svn:author</S:revprop><S:revprop>svn:date</S:revp
> rop><S:revprop>svn:log</S:revprop><S:path
> >
> > 48
The most interesting tag in here is
'><S:include-merged-revisions></S:include-merged-revisions>'
The limit and range are applied on the revisions retrieved, and then *all
merged revisions* are included. In some cases this can be a very large range of
merged revisions.
Bert
