| Age | Commit message (Collapse) | Author |
|---|
|
tests need some more work. Also, the tests need to be reorganized and move closer to their actual location within gitpython. Hence the refs tests go to git.test.refs, etc
|
|
more work as the amount of submodules changed in fact. Maybe I should just generate a test repository with gitpython as submodule to get the recursion depth required to satisfy the test
|
|
|
|
|
|
|
|
the test suggests. Pure python implementation still has some trouble, but this should be very fixable
|
|
of the new database types. This reduces code duplication to the mere minimum, but allows custom tests to be added on top easily and flexibly
|
|
methods on the default Repo implementation into interfaces or something that can be abstracted. It shows that it would indeed be good to keep the differentiation between Repositories which contain an object database as it is clearly easier to setup any combination of repositories that use git and those that do not, with just the addition of one more level of indirection. Lets see how it will end up
|
|
repo interface. Added submodule interface ... goal is to provide all of the extra repo functionality in custom interfaces
|
|
changed drastically. Now the actual work begins
|
|
|
|
Then the tests will need some work
|
|
submodule implementation is left in git-python as it requires some advanced features. No tests where run yet
|
|
git command. everything else was moved to GitDB. None of the tests is yet expected to run, although git-python should have less trouble getting the tests back up running than GitDB. plenty of code needs to be de-duplicated though in case of the tests, which will be some work
|
|
looked like hexshas. Thanks to Ning (frostyplanet) who pointed this issue out
|
|
remote: Fixed bug that was caused by the unchecked deletion of an uncached attribute which did not necessarily exist
|
|
tests may work.
Switched gitdb submodule to new github url
|
|
|
|
adjusted
|
