| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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
|
|
|
|
| |
messages - previously it would be more narrow and raise a GitCommandError in cases where it wasnt actually needed
|
|
|
|
| |
have not been updated as they where modified locally or did not exist. Test was improved to check for this new case.
|
| |
|
|
|
|
| |
processing - delays could have been possible previously as it would expand (possibly) large amounts of paths in advance
|
|
|
|
| |
code does not rely on my own git patch anymore as it is unsure whether it will make it in there or when
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Previously it would consider such a path a relative one and handle it incorrectly
|
|
|
|
| |
email address specified
|
|
|
|
| |
appears git-rev-list uses empty paths in some way, which is quite hard to specify on a shell, but easy if the process is spawned directly
|
|
|
|
| |
binary files went crazy as well as binary writing
|
|
|
|
|
|
| |
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 )
|
|
|
|
| |
finally causing failure in python 2.6
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
|
|
|
| |
backslashes depending on the operating system
fixed test_refs and test_trees
Many more issues remain though, this is just a first backup commit
|
|
|
|
| |
needs to be started
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* docs:
Converted tabs to spaces.
added paragraph about the diffing engine and how to switch branches, which once more shows the need for a real checkout for all the people who do not want to implement all the safety facilities themselves
Added Index Object paragraph and wrote the Remote Handling paragraph. Updated repo area
added paragraph about using the git-python command
Worked on the tree object handling and realized an issue with attribute naming on index objects and the way the system handles these
initial work on tutorial.rst
added all new files to reference.rst and corrected the worst mistakes. There are still a few errors left that I cannot fix as it complains about whitespace in the end ... that is exactly what I hate restructured text for, its just a ... anyway.
|
| |
| |
| |
| | |
are still a few errors left that I cannot fix as it complains about whitespace in the end ... that is exactly what I hate restructured text for, its just a ... anyway.
|
|/
|
|
| |
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
|
|
|
|
| |
file. This removes a git command invocation
|
|
|
|
| |
SymbolicReference.from_path creates only symbolic refs. This change was not detected by a test, hence there is room for improvement on the testing field
|
|
|
|
| |
reflog support. This should be manually implemented though for more performance, what it does is relatively easy
|
|
|
|
| |
only which is equivalent to waiting for an operation to finish completely. Now we parse the stream manually, allowing to retrieve progress information as soon as it happens
|
|
|
|
| |
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)
|
|
|
|
| |
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
|
| |
|