[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: <kmradke_at_rockwellcollins.com>
Date: Mon, 11 May 2009 10:01:26 -0500

Johan Corveleyn <johan.corveleyn_at_uz.kuleuven.ac.be> wrote on 05/09/2009
02:28:20 PM:
> > 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?
> >
> 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?

Unfortunately, no, I don't have any examples. It was just a wild
idea.

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

On unix, you can launch it in the background, but you would need to
worry about 2 jobs running at the same time, so simple locking would
be needed.

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

Yep.

Kevin R.

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

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-11 17:02:17 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.