| Age | Commit message (Collapse) | Author |
|---|
|
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
|
|
was added instead
Adjusted all imports to deal with the changed package names
|
|
but next there will have to be more through testing
|
|
multi-threading implementation of all odb functions
|
|
everything. Next is to implement pack-file reading, then alternates which should allow to resolve everything
|
|
parsing which truncated newlines although it was ilegitimate. Its up to the reader to truncate therse, nowhere in the git code I could find anyone adding newlines to commits where it is written
Added performance tests for serialization, it does about 5k commits per second if writing to tmpfs
|
|
efficiently considering that it copies string buffers all the time
|
|
from their object information directly. This is faster, and resolves issues with the rev-list format and empty commit messages
Adjusted many tests to go with the changes, as they were still mocked. The mock was removed if necessary and replaced by code that actually executes
|
|
performance is slightly better
git.cmd: added method to provide access to the content stream directly. This is more efficient if large objects are handled, if it is actually used
test.helpers: removed unnecessary code
|
|
objects if it could serialize itself
|
|
and absolute paths were given
Commit.create_from_tree: fixed critical bug that would cause it to create a branch named master by default, instead of the reference actually set ( which is master in many, but not all cases )
- in fact it could be detached as well, we would fail ungracefully although we could assume master then ... although we cant really make the decision
Repo.is_dirty: improved its abiility to deal with empty repositories and a missing head. Weird thing is that the test always worked fine with the previous code, but it didn't work for me in a similar situation without this change at least
|
|
on lighthouse.
README/intro.rst: added information about the new repository at github
tree: added marker to indicate that submodules would have to be returned there
|
|
This commit includes
- an update to git.objects.utils:parse_actor_and_date to parse the timezone offset
- updates to the git.objects.Commit and git.objects.Tag objects to support *_tz_offset attributes
- updates to tests in test.git.test_commit and test.git.test_refs to check for appropriate *_tz_offset attributes
|
|
|
|
to paths anymore as it will only append '--' if paths are actually given.
Added unittest to verify this
|
|
previous version was making assumptions that would only be true for old git repositories it sesms. The new version of the algorithm deals with this gracefully.
|
|
|
|
allowing the keys to contain slashes; adjusted test to check for this
|
|
safer to use in case of bare repositories
|
|
non-natural when using it
|
|
the item as well to enable predicates to do more proper checking
|
|
method, improved code performance by disabling the visit-once flag by default for trees, which by nature are not recursive
|
|
allowing the callee to know more about its environment
|
|
the first very pure implementation
|
|
Fixed critical bug in object code: IndexObjects now use their path as hashkey, not the data\!
|
|
including a test
|
|
IndexObject._mode_str_to_int: Now uses the 6 relevant bytes of the passed in octal string
|
