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

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

From: David James <james_at_cs.toronto.edu>
Date: 2007-05-09 19:37:08 CEST

On 5/9/07, Daniel Berlin <dberlin@dberlin.org> wrote:
> [... snip ...]
> Yeah, it may slow down if you log obscure directories with almost no
> changes. But i don't believe this is the common case.

How dramatic is the slowdown from your optimization if you run 'svn
log' on a file or directory which has few changes? From reading your
email, it seems like the slowdown will be very minor, but correct me
if I am wrong.

I do often run 'svn log --limit N' on an individual file or directory
to read about the last N changes to a particular file or directory. I
also find it handy to run "svn log -r1:HEAD --limit 1 --stop-on-copy"
to find the last revision in which a file was copied, or "svn log
-r1:HEAD --limit 1" to find the revision in which a file was created.
So far I haven't noticed any performance problems with these
operations, but if your change will have a dramatic effect on these
cases you might want to think about that.



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 9 19:37:21 2007

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