| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
Needs plenty of work
|
| |
|
|
|
|
| |
everything from the existing implementation, but one by one things can be reimplmented to use dulwich.
It also shows that py 2.6 is quite plagued from its new feature, which is actually a bug, as objects inability to accept any args makes mixins hard to use ...
|
| |
|
|
| |
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
|
| |
|
|
|
|
| |
implementations. It seems theoretically work together now, although it clearly is much more complex than ever before.
The repo package was slimmed down to being a module once again, which is only there for compatability actually
|
| |
|
|
| |
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
|
