| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
still a mess, it really needs to be separated into interfaces and implementations, sorted by type , like pure, pygit(at some point) and so on. This would already allow database implementations to be mixed and matched. One further step to be taken another day would be to 'interfacify' object and reference types, so they could be replaced by different implementations as well including full isinstance support (as isinstance would only check for the base interface). To ease this, the interfaces would just keep their original names, but the implementation would move to types like PureObject, PureSymbolicReference, etc. etc
|
| |
|
|
| |
with reference support, as opposed to a plain odb which objects are already happy with. Tests now work up to the point where a rev-parse is required. This could be helped, but revparse could also be implemented somewhere which was the reason for pulling in so much code in the first place
|
| |
|
|
| |
showed that we need to distinguish between plain object dbs with a respective interface and full repositories, which have references and remotes. Ideally, the ones that require only odbs use the odb member, others use the repo member
|
| |
|
|
| |
one still needs to be implemented, and integrated into type hierarchy to be actually useful. A test for the RepositoryPathsMixin would be required as well
|
| |
|
|
| |
git_dir() providing repository. Currently there is no separate interface for this, which might have to be added at some point just for the sake of completeness
|
| |
|
|
| |
the database for some reason.
|
|
|
running. Currently it requires an object implementation which will be ported next. None of the tests is expected to run yet.
|
