| Age | Commit message (Collapse) | Author |
|---|
|
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
|
|
as sha, even if the passed in id was a ref. This is done to assure objects are uniquely identified and will compare correctly
|
|
a convenient shortcut to using the classes manually
|
|
all parameters to be used. The test would not test everything either, and I would consider this a bug that slipped through
|
|
studied, but they would be hard to 'produce'
|
|
|
|
many more test-cases need to be added to be sure we can truly deal with everything git throws at us
|
|
|
|
proven now that this is not happening if stderr is being redirected. A test is in place that will most likely fail in case this ever changes
|
|
nice to use)
|
|
unfortunately, deepening the repository fails if the server is used. This is bad, but a workaround is to create another shared repo which pushes a changes that we fetch into our given repo. This should provide more output to properly test the fetch handling. Harder than I thought
|
|
incorrect as it cannot always work
|
|
are to be added it cluttered up the view and made things more complex as well
|
|
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
|
|
but it will assuambly follow with the push tests
|
|
dealing with deletion and movements of remote tags ( which in fact is discouraged, but we should be able to deal with it, shouldnt we ;)
|
|
handle the FETCH_HEAD case and
handle tags
System needs to be adjusted to take the FETCH_HEAD info into account to cover the tags case
|
|
handling and deletion of stale remote branches
|
|
stripping
|
