| Age | Commit message (Collapse) | Author |
|---|
|
usable. It showed that the ConfigParser needs some work. If the root is set, it also needs to refer to the root_commit instead of to the root-tree, as it will have to decide whether it works on the working tree's version of the .gitmodules file or the one in the repository
|
|
instead of the existing and valid. The rest of the ConfigParser handling is correct, as it reads all configuration files available to git
see http://github.com/Byron/GitPython/issues#issue/1
|
|
the submodules's naming conventions
|
|
use 20 byte sha's internally as it is closer to the GitDB implementation
Switched all remaining files back to tabs
Adjusted all remaining docstrings to suit the sphinx doc convention - its likely that there are many of docstring syntax errors though
|
|
|
|
uses a 'failing' lock file, but now its possible to easily put a blocking lock file in its place
|
|
remote.config: SectionConstraint now knows about set_value and get_value which are new to the GitConfigParser
|
|
|
|
|
|
queries to the git configuration, returning a value in the proper type. In a way its not supposed to be used as you should know the type of your configuration option or get an exception otherwise
|
|
finally causing failure in python 2.6
|
|
GitConfigFile is now derived from LockFile using its capabilities
Implemented ConcurrentWriteOperation, test is yet to be done
|
|
continuation lines - this leads to very incorrect results when parsing git config files. Now the complete reading is overridden to make it work as there was no other way
|
|
config: fixed issue that would cause it to abort reading if the file did not exist - this is valid now
Test does not work as the configuration parsing does not work as expected - this must be fixed first
|
|
reading, all tests work
|
|
Added odict module to get an OrderedDict to be used in the config parser, assuring the order of sections and options does not change
|
|
tests - most of which still has to be filled out
|
