search

tomheon / git_by_a_bus

Analyze your git repo for developers with unique knowledge.
83 stars 14 forks source link

Should take a digest to mark a point in repo #7

Open groby opened 9 years ago

groby commented 9 years ago

When processing a huge repository, git-by-a-bus takes.... long. Very long. Since it's not tied to a specific SHA-1 when it runs, I can't update the tree while it's running, which blocks any work.

tomheon commented 9 years ago

Hi @groby, thanks for the report.

So, 2 things:

1 of 2) gbab does indeed take a long time--sometimes pathologically long.

2 of 2) however, if the problem with the run time in your case is that you can't work on the directory in question, I think a cheap workaround is just to clone the repo locally and work off the clone (unless I'm misunderstanding or missing something of course).

3 of 2) The tragically long delayed v2 fixes many performance problems but has some others. If you want to try running that on your repo, let me know and I'll walk you through it.