| Age | Commit message (Collapse) | Author |
|---|
|
is actually more efficient than the previous implementation
Index now locks its file for reading, and properly uses LockedFD when writing
|
|
|
|
was added instead
Adjusted all imports to deal with the changed package names
|
|
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
|
|
appears to be working
|
|
containing the lock was removed. This is unlikely to happen in a production envrironment, but may happen during testing, as folders are moved/deleted once the test is complete. Daemons might still be waiting for something, and they should be allowed to terminate instead of waiting for a possibly long time
|
|
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
|
|
|
|
exists. Previously it would just fail
|
|
order to make it impossible for threads to overwrite each other if we are talking about miliseconds. This renders plenty of 'special' handling redundant
|
|
locks will check whether the lock they wrote truly is theirs - in case threads are racing, this might not be the case. Now this issue will be detected and results in a proper failure
|
|
uses a 'failing' lock file, but now its possible to easily put a blocking lock file in its place
|
|
caused lockups while waiting for stdout
NOTE: This does not have the desired effect, the issue appears to be somewhere within git, possibly, as git simply does not terminate waiting for something, even if stdout is closed.
|
|
exist more gracefully
Added BlockingLockFile which may be used to wait for the lock according to some criteria
|
|
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)
|
|
cannot be reamed using the git-branch command if they are not in refs/heads, that is in a non-standard refs folder
|
|
safer to use in case of bare repositories
|
|
binary files went crazy as well as binary writing
|
|
backslashes depending on the operating system
fixed test_refs and test_trees
Many more issues remain though, this is just a first backup commit
|
|
constructs, previously it was remote.refs['%s/master'%remote]
Added first simple test for push support, which shows that much more work is needed on that side to allow just-in-time progress information
|
|
fashion comparable to the native implementation
|
|
|
|
GitConfigFile is now derived from LockFile using its capabilities
Implemented ConcurrentWriteOperation, test is yet to be done
|
|
valid indices after manually removing or altering entriesgst
|
|
the respective modules that use them
fixed repo.daemon_export which did not work anymore due to incorrect touch implementation and wrong property names
|
|
simple tests
|
|
preparation for command changes
|
|
|
|
to dynamically retrieve their objects
Improved way commits are returned by refs as they now use the path to be sure they always point to the ref even if it changes - previously it would use the sha intead so it would not update after being cached on the ref object
|
|
editor to work with the files properly. Can convert it back for releaes
|
|
|
|
|
|
http://groups.google.com/group/git-python/browse_thread/thread/b8f3580abf31f9db?hl=en# and passed Git a working_tree again (sort of).
|
|
up tests so they pass except for stderr test. Modified version information retrieval.
|
