This class takes the initialization variable "global_only" which
will be set in the future whenever multiple repositories are
specified (See issue #24).
This will make sure that the git configuration is only read from the
global settings instead of per-repository.
It now correctly references the current pot and version. Consequently, it
should be usable without generating a warning from the current
development iteration of gitinspector.
This commit updates the German translation. Changes in translation
include updating for changed messages in upstream and some rewording.
Also, this commit includes a different translation for "cyclomatic
complexity" because the previously used one (by inventor's name)
might be less clear than the current, literal translation, which seems
more intuitive, especially in a world where English is dominant in
software dev, so people are more likely to know only the English word.
Some translations have been changed to be more clear and to the point.
Some comments have been added to messages that have been causing issues.
With this change, gitinspector once again functions in conjunction with
egg installations. Also removed all forceful absolute imports, as these
really aren't needed.
This prepares the source code for the changes discussed in issue #24.
Note that this is just a quick restructuring in order to see the resulting
classes and separation. More work will be done to make it more elegant
and with less dependencies between modules.
While allowing us to include translations that are not quite up to date
with the current development branch in releases, it also serves to inform
the user that they are using a translation that is broken or incomplete.
The only thing that has changed since the last .pot file is the help text
(--help). New text has been added to the documentation for the "-x" flag
and the "-f" flag.
This functionality was briefly discussed in issue #61. To make
gitinspector consider all file extensions, it is now possible to supply
a double asterisk "**" to the list of file extensions.
Once again introduced with aeb9ad6, this could happen whenever a
repository had no commits or if the history was being filtered with
--since and/or --until and no commits were being detected within that
interval.