summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* Improved debug assertion to provide proper path on which to run a git daemonSebastian Thiel2011-06-081-2/+4
|
* git.version_info now returns exactly 4 numbersSebastian Thiel2011-06-081-2/+4
|
* log: non-existing logs no longer throw an exception, but are ignored. Fixed ↵Sebastian Thiel2011-06-083-5/+17
| | | | critical bug which caused packed-ref files to be written with native line endings, which made git fail to parse it. I wonder why I never noticed this before, or ignored it. Unbelievable \!
* Merge branch 'gitdbmerger'Sebastian Thiel2011-06-07122-2935/+10035
|\
| * Added additional opcodes to remote progress to make it compatible to newer ↵Sebastian Thiel2011-06-073-16/+26
| | | | | | | | git versions. This bug existed for quite a while but didn't show up as progress wasn't sent most of the time. All methods that could use a progress will only activate it if a progress is actually given
| * Greatly improved robustness of config parser - it can now take pretty much ↵Sebastian Thiel2011-06-073-10/+23
| | | | | | | | everything. Includes an updated config file which includes all the new additions
| * Match any number of leading spaces in config valuesJesse Keating2011-06-071-1/+1
| | | | | | | | | | | | The regex comments state that any number of leading tabs or spaces should be allowed, however the regex was only catching zero or one space. This allows multiple spaces.
| * Making comparisons with non-GitPython objects more tolerant.Julien Miotte2011-06-071-0/+4
| |
| * The --progress flag will now automatically be used if possible when doing ↵Sebastian Thiel2011-06-071-4/+14
| | | | | | | | any push or fetch operation
| * submodule now doesn't use hardcoded repository implementations anymore. ↵Sebastian Thiel2011-06-071-5/+9
| | | | | | | | Instead it allows the user to override the type in the classmethod he calls. Otherwise the type of the own repo will be respected
| * Submodule tests are fully back and workingSebastian Thiel2011-06-071-18/+28
| |
| * Submodule tests are nearly working. Only root module needs more attentionSebastian Thiel2011-06-072-14/+36
| |
| * Fixed index checkout return code parsing to work with latest git versionSebastian Thiel2011-06-071-0/+4
| |
| * First run in order to fix the remote handling. Cleaned up interfaces and ↵Sebastian Thiel2011-06-079-630/+642
| | | | | | | | figured out that the implementation really should be specific to the git command. This leaves the interface open for other implemntations which use a different way to provide feedback (as we do not make assumptions about the format of a feedback line)
| * clone and clone_from methods now support the RemoteProgress interface, using ↵Sebastian Thiel2011-06-073-105/+115
| | | | | | | | similar functionality as used by the fetch, push and pull methods
| * Added version_info property to git commandSebastian Thiel2011-06-073-6/+33
| |
| * Fixed fetch/push/pull implementation. Next up is to integrate the ↵Sebastian Thiel2011-06-072-14/+25
| | | | | | | | consolidation changes from master to make clone use the same facilities
| * Improved pack writing test to show that the pack generation can be lightning ↵Sebastian Thiel2011-06-061-21/+28
| | | | | | | | fast with nearly now overhead if the data streams in fast enough (~30 MB/s when writing a pack). This shows that there is huge potential for sending packs, considering that we are actually recompressing them (without deltification). To be faster in future, we could probably just send ref-deltas or full objects as found in the pack without doing any recompression.
| * Streams returned by git cmd db are now containing all the data right away. ↵Sebastian Thiel2011-06-062-4/+14
| | | | | | | | This could cause several copies to exist, and makes the cmd implementation a bad choice if big files are involved
| * Fixed performance pack writing tests. As they are actually depent on the ↵Sebastian Thiel2011-06-062-80/+76
| | | | | | | | database (as streams have to be decompressed, it should be redesigned to have multiple database implementations)
| * Moved performance commit object test into the respective subfolder to ↵Sebastian Thiel2011-06-062-1/+2
| | | | | | | | indicate what it tests
| * Fixed performance commit object testingSebastian Thiel2011-06-063-8/+10
| |
| * Added loose object writing and reading performance tessts, in pure and ↵Sebastian Thiel2011-06-065-312/+166
| | | | | | | | command implementations. The previous performance test was truncated a bit as it compared directly with the git hash_object write performance. This is out, and if we wanted it we could implement it , but its actually slower for us
| * Added PackedDB test with generalized type to allows other implementations to ↵Sebastian Thiel2011-06-063-7/+21
| | | | | | | | be tested as well at some point
| * Fixed packed ODB test, in preparation for separating the type to allow ↵Sebastian Thiel2011-06-063-6/+21
| | | | | | | | future implementations to use the test as well
| * Fixed odb performance testsSebastian Thiel2011-06-068-94/+102
| |
| * Fixed symref tests to work on osxSebastian Thiel2011-06-011-3/+2
| |
| * Fixed ref-log related issue in the test suite to assure it will not give ↵Sebastian Thiel2011-06-011-2/+9
| | | | | | | | false positives in repositories that are freshly checked out
| * Fixed remaining tests as good as possible. remote/fetch/pull and submodule ↵Sebastian Thiel2011-05-3018-137/+191
| | | | | | | | 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
| * Fixed all of the object tests, except for the submodule handling which needs ↵Sebastian Thiel2011-05-306-15/+41
| | | | | | | | 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
| * Fixed all remaining python repository testsSebastian Thiel2011-05-309-64/+77
| |
| * Fixed test_loose.pySebastian Thiel2011-05-301-3/+5
| |
| * Fixed test_git.pySebastian Thiel2011-05-301-8/+12
| |
| * Fixed pure python implementation to run the default repository testsSebastian Thiel2011-05-303-12/+11
| |
| * git cmd implementation of repository appears to work, at least this is what ↵Sebastian Thiel2011-05-3021-83/+118
| | | | | | | | the test suggests. Pure python implementation still has some trouble, but this should be very fixable
| * Fixed tests far enough to allow basic repository tests to be applied to any ↵Sebastian Thiel2011-05-3021-65/+152
| | | | | | | | 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
| * Finished moving all repository methods to the respective interfaces and ↵Sebastian Thiel2011-05-3012-863/+936
| | | | | | | | | | | | 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
| * Intermediate commit with quite some progress in order to put all extra ↵Sebastian Thiel2011-05-2911-689/+650
| | | | | | | | 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
| * Made repository paths methods a property to be compatible with the existing ↵Sebastian Thiel2011-05-1014-80/+234
| | | | | | | | repo interface. Added submodule interface ... goal is to provide all of the extra repo functionality in custom interfaces
| * Started to fix imports - tests still have no chance to work as database ↵Sebastian Thiel2011-05-0642-91/+1461
| | | | | | | | changed drastically. Now the actual work begins
| * replaced all gitdb strings with gitSebastian Thiel2011-05-0652-144/+148
| |
| * removed gitdb submoduleSebastian Thiel2011-05-062-4/+0
| |
| * Added all code from gitdb to gitpython. Next is to make it generally work. ↵Sebastian Thiel2011-05-0564-197/+9917
| | | | | | | | Then the tests will need some work
| * Added async submodule, formerly required by gitdb (which is still a valid ↵Sebastian Thiel2011-05-053-3/+6
| | | | | | | | submodule just yet)
| * Made most primal imports work, but stopped here as there are many more ↵Sebastian Thiel2011-05-059-15/+20
| | | | | | | | changes when doing the merge
| * Moved rev_parse code into gitdb, this probably broke pretty much here, which ↵Sebastian Thiel2011-04-2910-332/+20
| | | | | | | | is still to be fixed of course
| * configparser is now part of gitdb. Test still remains until it was replaced ↵Sebastian Thiel2011-04-253-1785/+3
| | | | | | | | by its gitdb counterpart through inheritance. All items which are part of gitdb but used by gitpython need their own verification within gitpython
| * Updated objects to use the ones defined in gitdb as basis. Only the ↵Sebastian Thiel2011-04-0714-1068/+37
| | | | | | | | submodule implementation is left in git-python as it requires some advanced features. No tests where run yet
| * Removed all parts of the reference implementation which doesn't require the ↵Sebastian Thiel2011-04-0713-1473/+86
| | | | | | | | 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
| * Moved push and fetch methods partly from remote to the gitcmdobjdb ↵Sebastian Thiel2011-04-055-337/+393
|/ | | | 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
View Lorry Controller Status