Re: log --limit not as good as it should be?

Daniel Berlin wrote:
> (This is running against a 1.5.0 dev build server, so the server
> definitely supports the limit stuff. The same behavior is also found
> running against http)
>
> svn log -r 1:400 --limit 400 svn://gcc.gnu.org/svn/gcc/trunk
>
> This will respond immediately and produce 400 revisions of log output
>
> svn log -r 1:HEAD --limit 400 svn://gcc.gnu.org/svn/gcc/trunk
>
> This will take about 3-4 minutes before starting to respond, and
> produce the same 400 revisions of log output.
>
> It looks like something is touching all the revisions that *might* be
> logged before we start producing log output at all.

Yes. We can only trace history backwards, so anytime you run a log request
with oldest-to-youngest direction in your range, the revisions have to be
determined up front, then reported in reverse.

Your first command gathers all the changed revs between 400 and the revision
in which the path came into being, then reports the first 400 of them in
reverse.

You second command gathers all the changed revs between HEAD and the
revision in which the path came into being, then ports the first 400 of them
in reverse.

-- 
C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand