summaryrefslogtreecommitdiff
path: root/lib/git/ext/gitdb
Commit message (Collapse)AuthorAgeFilesLines
* moved all contents, incl. submodule gitdb, up to the root directorySebastian Thiel2010-11-211-0/+0
|
* Added zip_safe info to setup.py fileSebastian Thiel2010-11-211-0/+0
|
* Updated gitdb submodule, and added note about how the submodule package ↵Sebastian Thiel2010-11-191-0/+0
| | | | manages its dependencies
* submodule: Fleshed out interface, and a partial test which is not yet ↵Sebastian Thiel2010-11-151-0/+0
| | | | usable. It showed that the ConfigParser needs some work. If the root is set, it also needs to refer to the root_commit instead of to the root-tree, as it will have to decide whether it works on the working tree's version of the .gitmodules file or the one in the repository
* Added test to verify the actor type can handle and parse unicode if it is ↵Sebastian Thiel2010-10-151-0/+0
| | | | | | passed in test_odb: added more information to the message output
* unicode handling in messages and trees was improved. Messages are now ↵Sebastian Thiel2010-08-131-0/+0
| | | | written according to the encoding of the commit object, and decoded using that information as well. Trees will encode and decode their names with utf8
* Index._iter_expand_paths: fixed tiny error with large impact, there was code ↵Sebastian Thiel2010-07-151-0/+0
| | | | using a / in a hardcoded fashion, leading to absolute paths where the caller expected relative ones
* Added performance test to compare inst.__class__() vs type(inst)() class. ↵Sebastian Thiel2010-07-141-0/+0
| | | | The first one is faster, although I would have expected the latter one to be faster
* Added python 2.4 support: Repo will now use the original GitCmdObjectDB in ↵Sebastian Thiel2010-07-091-0/+0
| | | | python 2.4, as the pure python implementation cannot work without memory maps
* setup.py: fixed requirement - its interesting to see that there are two ↵0.3.0-beta1Sebastian Thiel2010-07-081-0/+0
| | | | different keywords for distutils and setuptools, the latter one doesn't read the ones of the first one, unfortunately
* Initially working implementation of short-sha parsing and interpretation, ↵Sebastian Thiel2010-07-071-0/+0
| | | | thanks to new gitdb functionality
* Initial version of the rev-parse routine, which doesn't work too bad, but ↵Sebastian Thiel2010-07-061-0/+0
| | | | its still rather slow and many tests are not yet implemented
* win32 compatability adjustmentsunknown2010-07-021-0/+0
|
* Fixed broken 0.2 documentation, it didn't contain the API reference ↵Sebastian Thiel2010-07-021-0/+0
| | | | previously due to import errors and a somewhat inconsistent working tree that occurred when switching branches ...
* Added further information about the required submodules, and how to install ↵Sebastian Thiel2010-07-011-0/+0
| | | | them. Incremeneted version to 0.3.0 beta1
* Diff: fixed bug that caused a string to end up as a blob modeSebastian Thiel2010-06-291-0/+0
|
* Adjusted all files to (hopefully) deal with the fact that all objects now ↵Sebastian Thiel2010-06-251-0/+0
| | | | | | | use 20 byte sha's internally as it is closer to the GitDB implementation Switched all remaining files back to tabs Adjusted all remaining docstrings to suit the sphinx doc convention - its likely that there are many of docstring syntax errors though
* index.reset is now partly implemented using python, but in fact it resorts ↵Sebastian Thiel2010-06-251-0/+0
| | | | to using git-read-tree to keep the stat information when merging one tree in. After all this is what needed to be implemented in python as well
* aggressive_tree_merge: fixed incorrect handling of one branch, it was just ↵Sebastian Thiel2010-06-241-0/+0
| | | | | | not implemented causing incorrect merge results. Added test to cover this issue Diff: added NULL_BIN_SHA constant for completeness
* index.write_tree: now uses MemoryDB, making tree handling more efficient as ↵Sebastian Thiel2010-06-221-0/+0
| | | | IO will only be done when required. A possible disadvantage though is that time is spent on compressing the trees, although only the raw data and their shas would theoretically be needed. On the other hand, compressing their data uses less memory. An optimal implementation would just sha the data, check for existance, and compress it to write it to the database right away. This would mean more specialized code though, introducing redundancy. If IStreams would know whether they contain compressed or uncompressed data, and if there was a method to get a sha from data, this would work nicely in the existing framework though
* db: added pure python git databaseSebastian Thiel2010-06-201-0/+0
| | | | repo: now has the option to use the pure python git database implementation, which is currently not used though
* GitCmd implementation of gitdb base moved to git-python where it belongs. ↵Sebastian Thiel2010-06-181-0/+0
| | | | Previously it was located in gitdb, which doesn't have any facilities to use the git command
* Move LazyMixin type to gitdb, index reading now uses file_contents_ro from ↵Sebastian Thiel2010-06-151-0/+0
| | | | gitdb as well
* Moved LockedFD and its test into the gitdb projectSebastian Thiel2010-06-151-0/+0
|
* Reimplemented Lock handling to be conforming to the git lock protocol, which ↵Sebastian Thiel2010-06-151-0/+0
| | | | | | is actually more efficient than the previous implementation Index now locks its file for reading, and properly uses LockedFD when writing
* Implemented initial version of tree serialization which appears to work ↵Sebastian Thiel2010-06-141-0/+0
| | | | | | | according to a simple test ( presort still needs implementation ) submodule: added stub to allow the tree to return something, its not implemented though
* Removed odb from project, it is now used as a submodule named gitdb, which ↵Sebastian Thiel2010-06-121-0/+0
was added instead Adjusted all imports to deal with the changed package names
View Lorry Controller Status