| Age | Commit message (Collapse) | Author |
|---|
|
|
|
right, but its not yet tested
|
|
|
|
the restricted tests are concerned
|
|
submodule removals, as well as url changes
|
|
moved later if the configuration changed, and actually it also verifies that the url-change is handled correctly (as we changed the url from the default to the local path)
|
|
|
|
being a special case of the commit method; includes tests
util: Fixed iterable lists, which broke due to an incorrectly implemented __contains__ method
|
|
the ORIG_HEAD reference as well
|
|
able to handle submodule removals, additions, path changes and branch changes. All this still needs to be tested though
|
|
property alrdeady
Improved submodule move tests
|
|
to-be-improved test
|
|
coverage for it
|
|
|
|
fixed a few issues on the way
|
|
next
|
|
|
|
to update submodules such as svn-externals
|
|
|
|
though to allow easy configuration of branch-specific settings
|
|
svn-external like behaviour. Implemented first version of update, which works for now, but probably needs to see more features
|
|
general may be contradicting if a tag is given there, as well as a commit sha of the submodule. Hence it should really be only a branch
|
|
was mainly copy-paste from with_rw_repo, what a shame
|
|
provided for Remotes, including test
|
|
local cache - previously a procedural approach was used, which was less code, but slower too. Especially in case of CommitObjects unrolling the loop manually makes a difference.
Submodule: Implemented query methods and did a bit of testing. More is to come, but the test works for now. As special addition, the submodule implementation uses the section name as submodule ID even though it seems to be just the path. This allows to make renames easier
|
|
corresponding locks. Submodule class now operates on parent_commits, the configuration is either streamed from the repository or written directly into a blob ( or file ) dependending on whether we have a working tree checkout or not which matches our parent_commit
|
|
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
|
|
instead of the existing and valid. The rest of the ConfigParser handling is correct, as it reads all configuration files available to git
see http://github.com/Byron/GitPython/issues#issue/1
|
|
into the byte stream, as well as decoded from it
|
|
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
|
|
method now yields good results on all tested platforms
|
|
it. Its can be assumed though that there are more bugs related to unicode hanging around in the system
|
|
rev_parse could be adjusted not to return Objects anymore, providing better performance for those who just want a sha only. On the other hand, the method is high-level and should be convenient to use as well, its a starting point for more usually, hence its unlikely to call it in tight loops
|
|
its still rather slow and many tests are not yet implemented
|
|
|
|
the rule of trying not to cache possibly heavy data. The data_stream method should be used instead
|
|
the submodules's naming conventions
|
|
|
|
|
|
|
|
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
|
|
was actually empty. This is a rare case that can happen during stream testing. Theoretically there shouldn't be any empty streams of course, but practically they do exist sometimes ;); fixed stream.seek implementation, which previously used seek on standard output
Improved GitCmd error handling
|
|
including simple test, it may be simple as the methods it uses are throroughly tested
|
|
can do much more than we can ( and faster assumably ), the .new method is used to create new index instances from up to 3 trees.
Implemented multi-tree traversal to facilitate building a stage list more efficiently ( although I am not sure whether it could be faster to use a dictionary together with some intensive lookup ), including test
Added performance to learn how fast certain operations are, and whether one should be preferred over another
|
|
correctly, a test to explicitly compare the git version with the python implementation is still missing
Tree and Index internally use 20 byte shas, converting them only as needed to reduce memory footprint and processing time
objects: started own 'fun' module containing the most important tree functions, more are likely to be added soon
|
|
information to just the stage ( just to be closer to the git-original )
|
|
|
|
fast, while staying compatible with serialization which requires it to be sorted
|
|
information - this also speeds up later serialization after changes. its clear though that retrieving actual objects is slower currently as these are not cached anymore. Its worth thinking about moving these encoding, decoding routines to gitdb
|
|
according to a simple test
( presort still needs implementation )
submodule: added stub to allow the tree to return something, its not implemented though
|
