| Age | Commit message (Collapse) | Author |
|---|
|
multi-threading implementation of all odb functions
|
|
|
|
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
|
|
|
|
missing ) and added performance tests which are extremely promising
|
|
efficiently considering that it copies string buffers all the time
|
|
|
|
appears to be working
|
|
objects will be written using our utilities, and certain object retrieval functionality moves into the GitObjectDatabase which is used by the repo instance
Added performance test for object database access, which shows quite respectable tree parsing performance, and okay blob access. Nonetheless, it will be hard to beat the c performance using a pure python implementation, but it can be a nice practice to write it anyway to allow more direct pack manipulations. Some could benefit from the ability to write packs as these can serve as local cache if alternates are used
|
|
bug of course which just didn't kick in yet
|
|
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
|
|
tests to work on larger repositories
|
|
|
|
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
|
|
convenience)
|
|
newline at the end of the split line was not split away automatically. Added test for this, and the trivial fix
Wow, at least two people reviewd the code, but it slipped through anyway :)
|
|
Cmd: AutoInterrupt handles boundary cases more gracefully as it can be that the os module suddenly becomes None if the interpreter is going down
|
|
|
|
different path in the index than the actual one on disk ( from which the object will be created )
Fixed bug the way newlines were handled, which hopefully fixes occasional hangs as well. It works fine with git 1.7.1
Most of the changes are due to the tab-space conversion - its weird once more as I thought it was all in spaces before ... .
|
|
repo.is_dirty: Will not fail on empty repo ( anymore )
index.entries: will just be empty if the repository is empty
refs: added to_full_path method which can be used to create fully synthetic instances of Reference types, added a test for it
Converted all touched files to spaces, which is why git reports so many changed files. Actually I was thinking every file would use spaces, but apparently not
|
|
Fixed test which required to be on master to work - it now uses the HEAD symbolic ref instead.
|
|
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
|
|
mistaken for disabled tests, although they are actually called by the test cases as utility functions
|
|
|
|
to paths anymore as it will only append '--' if paths are actually given.
Added unittest to verify this
|
|
test.helpers: temporary rw repository creators now set the working dir of the program, easing working with relative paths a lot
|
|
regarding its parents
|
|
Repo.init: fixed incorrect use of the path which was to optionally specify where to initialize the repository. Update test as well
|
|
available at some point natively, within the git suite
Progress parsing now deals properly with Ascii_Escape characters that are meant for the tty - git might stop sending this at some point, but we can deal with it no matter what
|
|
allowing the keys to contain slashes; adjusted test to check for this
|
|
uses a 'failing' lock file, but now its possible to easily put a blocking lock file in its place
|
|
|
|
exist more gracefully
Added BlockingLockFile which may be used to wait for the lock according to some criteria
|
|
remote.config: SectionConstraint now knows about set_value and get_value which are new to the GitConfigParser
|
|
|
|
|
|
failure as well, one per failed file
|
|
paths - previously it would run into a code-branch I forgot
|
|
Ref(anytype) Iteration was improved such that automatic filtering now also works for SymbolicReferences ( which only return symbolic refs)
|
|
only really knew heads, now we know references as a common base. The adjustment make the ref system as flexible as it was originally meant to be
|
|
has the same content as the new reference
|
|
the destination contains different data. If it contains the same, the move will work as we can do what the user intended
|
|
cannot be reamed using the git-branch command if they are not in refs/heads, that is in a non-standard refs folder
|
|
queries to the git configuration, returning a value in the proper type. In a way its not supposed to be used as you should know the type of your configuration option or get an exception otherwise
|
|
safer to use in case of bare repositories
|
|
repository was initialized with a .git repository, although it was not bare actually
|
|
index easier
|
|
only paths
diff.__str__: fixed incorrect message generation error
|
|
'Reference' implementation now shares all the code from the SymbolicReference base. This implementation allows to create any reference you'd like without requireing git calls
|
