| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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
|
|
|
|
| |
changed drastically. Now the actual work begins
|
| |
|
|
|
|
| |
changes when doing the merge
|
|
|
|
| |
is still to be fixed of course
|
|
|
|
| |
self.head.* in order to more safely get the current commit. active_branch would only work on non-detached heads
|
|
adjusted
|