| Age | Commit message (Collapse) | Author |
|---|
|
|
|
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
|
|
object. They are only constrained to be located in the refs/ directory
|
|
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
|
|
Fixed critical bug in object code: IndexObjects now use their path as hashkey, not the data\!
|
|
including a test
|
|
appear litereally anywhere. A 'default' reference is nothing more than a detached symbolic reference.
Added method iterate the packed refs file
|
|
restriction anymore.
Added a test to assure the git commands can handle it
|
|
any of our changes entries as it would in fact write a possibly cached tree stored in our extension data.It was solved by simply ignoring that extension data when writing the index for tree creation. A test was added for this as well
|
|
Index.checkout: fixed bug in exception creator function
|
|
trigger an error
|
|
index.write_tree may now use the missing_ok argument which writes trees faster and allows you to operate without objects to do a true index based merge
|
|
fast_forwards although. Renamed cumbersome 'commit_before_forced_updated' attribute to 'old_commit' to be en par with PushInfo
|
|
exact information about the successfully checked out files as well as the failed ones
Return value of the method is an iterator to all checked out files
|
|
have not been updated as they where modified locally or did not exist. Test was improved to check for this new case.
|
|
|
|
just in time
This adds a dependency to a git update index fix - and I hope it will be put in in time ( including windows version )
|
|
symlinks.
Added index.get_entries_key method to allow direct access to anyone willing to do so
|
|
branch, it will now create it if necessary
|
|
adjustment, but it works as expected even on systems that do not support symlinks
|
|
binary files went crazy as well as binary writing
|
|
namely 141 instead of 143. Manual checking showed that 143 is the correct number, on linux this will have to be fixed
|
|
os.remove by changing the mode to 777 and delete the file again. Otherwise the whole operation would fail on read-only files. Why is windows as it is ? Why does it do that to me ?
|
|
implementation in the end whether pipeing large input works. In general , input and output pipes are used, the shell is bypassed, hence there is no reason for a problem unless we are on a very rare platform. And if so, we can't do anything about it so why should there be a possibly failing test ? Problem is that the test would fail on windows in case it is not installed on c:\windows
|
|
as expected. Its quite terrible to see a two-line method inflate to 20
as there is no git-daemon on windows, some tests will not work. The error message has been adjusted to be more precise for the poor people trying to run the tests on windows ( including myself )
|
|
cmd: taskkill now pipes stderror to nul as well
|
|
persistent commands are killed before trying to remove the directory. Unfortunately, it still claims someone has opened the file. handle.exe does not show anyone, so what is happening here ? Is it just a windows odity ? If nothing helps I could just keep the temp data, but lets do some more testing first
|
|
needs to be started
|
|
head.checkout functions for greater ease of use - they work exactly as expected now.
Fixed failing test in remote tests by actually removing the line
|
|
|
|
one was made faster by reducing the amount of permutations to the minimal value
|
|
object
repo.tree: improved to be less restricting
|
|
previously it would just be a name )
added abspath property and name property to provide easy access to most common paths of an index object
|
|
not implement the crazy sorting feature found in git-for-each-ref though
|
|
reflog support. This should be manually implemented though for more performance, what it does is relatively easy
|
