| Age | Commit message (Collapse) | Author |
|
|
|
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
|
|
changed drastically. Now the actual work begins
|
|
is still to be fixed of course
|
|
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
|
|
implementation, including related types. It doesn't yet work, and the omnipresence of the repo imposes a problem right now, as the required ref functionality is not yet part of the gitdb specification. theoretically, the whole ref implementation has to move into gitdb
|
|
used if you create a new blob
|
|
copatible to the RemoteProgress and should satisfy all progress needs. Dryrun will be useful in conjunction with the progress to verify the changes to be done
|
|
|
|
entries, including test
|
|
support which cannot be exposed using the respective property. Ref-Creation is now fully implemented in python. For details, see doc/source/changes.rst
|
|
supported, mainly because I don't need it
|
|
|
|
|
|
Changes now give a hint at the upcoming release as well
|
|
into the byte stream, as well as decoded from it
|
|
docs: added changelog, which moved from the CHANGES file into sphinx
|