Adam Waldenberg

@imposeren Neither does it blame any files that have an invalid extension. Binary files are also skipped.

@imposeren Gitinspector starts as many processes as there are threads/cores. There is no configuration option for it, and never will be. However, there is a constant at the top of...

Hi @eddie-dunn. I'll keep it open and think about it. While it does not really help in evaluating an author, it might be useful.

@uli-weltersbach Yes it might be helpful. @eddie-dunn As stated before, yes I might be open to the idea. It's fits under the same scope as the already included metrics that...

Adding this to the 0.5.1 milestone.

Hi @GHardoim. Interesting. How does git itself react if you do a shortlog with the very same --since / --until flags ? What version are you using ? Please use...

Hi @GHardoim. So it seems perhaps that the introduction of "**" might have broken something. Could you do a "git bisect" run on the "extra-release/0.4.x" branch ? This should allow...

Hi @GHardoim. Thank you. Yes, that threading code introduced a few problems.... Can you test the master version ? There was a fix introduced in 6d77989e341e043c9a7f09757000d75701b32d84 - it may cover...

@GHardoim OK... So we probably have some logic error introduced with filtering and the threaded version of changes.py. I will look into it.

Hi @GHardoim If you start each instance recursively (with &) - yes. If you run gitinspector synchronously I don't think you should have a problem though.