[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Daniel Berlin <dberlin_at_dberlin.org>
Date: 2007-05-09 17:44:50 CEST

(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.

This is stlll true even if I use pegrevs (my first guess was that we
were trying to figure out what paths to actually log before we logged

I would have expected the two commands above to take the same amount
of time, assuming there are at least <limit> revisons to log.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 9 17:44:59 2007

This is an archived mail posted to the Subversion Dev mailing list.