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

RE: svn blame unworkably slow

From: Johan Corveleyn <johan.corveleyn_at_uz.kuleuven.ac.be>
Date: Sat, 9 May 2009 21:28:20 +0200

> I think someone else mentioned this before, but couldn't you pre-compute
> the blame output in a post-commit hook?  Then people would just go
> to a web page/network location to look at the blame output instead
> of running the blame themselves?
>
> Kevin R.

Thanks for the suggestion, Kevin. However, I've searched the archives, and couldn't any mention of this. Has anyone ever tried to do this? Any pointers or examples?

I'm not sure how one could do this. You can't do a lot of work in a post-commit hook, to avoid blocking the commit. So you'd have to spawn a new process to do it. Not that easy, I think ... But if anyone has a good solution for this, I'd really welcome an example.

Another approach would be doing it in a cron job (hourly/daily) for just those 2 very big files I have.

Oh and one more thing I found out while testing blame: the --diff-cmd option isn't supported by blame, and the config setting has no influence on it. I don't know how it works internally, so this might be normal. But it wasn't obvious to me (the help message from the svn client seems to indicate otherwise; it talks about "external diff program" when explaining the -x option).

Is this a minor documentation glitch, or is it something that "should be possible"?

Regards,
Johan

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2150480

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-09 21:29:45 CEST

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