Even though it is supported, PHP is not part of the default file extensions
used during analysis. To include PHP files in the statistical analysis,
the extension needs to be supplied to gitinspector using the -f flag.
The required Python version is 2.6. The check is done after all the
command-line arguments have been parsed. In this way, it is still possible
to get help and version information from the script even if the script is
not able to execute properly.
As we don't really need it, storing this was just eating up unnecessary
memory. On very big repositories (with many commits) removing it makes a
big difference.
Instead of manually adding this functionality with our own code; we use
the JQuery tablesorter plugin which adds support for sorting with a few
simple rows of code.
The printed data was using instead of spaces when printing out all
extensions found. This resulted in the browser not being able to properly
separate rows.
In practice, this means that the tables are initially collapsed and hide
all authors with a workload below one percent. The user can expand a
table in order to show all authors found during statistical analysis.
In practice, this means that whenever an author is not part of a
collection of periods he will not be printed out.
This cleans up the output and also speeds up analysis.
The output was simply wrong and was outputting extra "<authors>" tags all
over the place. Also, whenever there was very little work, this was not
included in the timeline.
Multi-line POD comments in Perl are not supported for now; they are a
little hairy and probably require a little extra work in order to be
parsed correctly.
This can now be done by supplying one (or both) of the "--since" and
"--until" parameters to the gitinspector executable. These parameters
work in the same manner as they do in git and accept the same values.
Statistics will only be generated from data between the given interval.
The call to git log included "'" characters to "stringify" input to the
git command. On unix systems, this functions the same way as the
citation (") character. On Windows however, it does not.
This bug occurred because whenever the "git blame" command detects
international character it outputs a string escaped character string in
the form "\ddd\ddd". Gitinspector didn't properly handle this. Python
offers a way to decode this using the decode function together with the
"string_escape" encoding.
Adam Waldenberg