| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
stripping
|
|
|
|
| |
reference paths
|
|
|
|
| |
expected. Plenty of cases still to be tested
|
|
|
|
| |
type of the actual class. This could result in a symbolic reference returned even though you technically requested a reference - this issue must still be addressed.
|
|
|
|
| |
remote: prepared FetchInfo class to be returned by fetch and pull. About to implement tests
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* index:
index.add: Finished implemenation including through tests
When parsing trees, we now store the originan type bits as well, previously we dropped it
cmd.wait: AutoKill wrapped process will automatically raise on errors to unify error handling amongst clients using the process directly. It might be needed to add a flag allowing to easily override that
added head kwarg to reset and commit method, allowing to automatically change the head to the given commit, which makes the methods more versatile
refs.SymoblicRef: implemented direcft setting of the symbolic references commit, which possibly dereferences to the respective head
index.commit: implemented initial version, but in fact some more changes are required to have a nice API. Tests are not yet fully done either
actor: added __eq__, __ne__ and __hash__ methods including simple test
index.remove implemented including throrough test
Implemented index.reset method including test
IndexEntry is now based on a 'minimal' version that is suitable to be fed into UpdateIndex. The Inode and device information is only needed to quickly compare the index against the working tree for changes, hence it should not be that dominant in the API either. More changes to come
Added notes about git-update-ref
Refs can now set the reference they are pointing to in a controlled fashion by writing their ref file directly
Added TagRefernce creation and deletion including tests
Implemented head methods: create, delete, rename, including tests
refs: added create, delete and rename methods where appropriate. Tests are marked, implementation is needed for most of them
Added frame for IndexFile add/remove/commit methods and respective test markers
Added repo.index property including simple test, and additional ideas in the TODO list
Renamed Index to IndexFile, adjusted tests, it will only operate on physical files, not on streams, as Indices are not streamed by any git command ( at least not in raw format )
|
| |
| |
| |
| | |
index.checkout: added simple method allowing to checkout files from the index, including simple test
|
| |
| |
| |
| | |
we dropped it
|
| |
| |
| |
| | |
unify error handling amongst clients using the process directly. It might be needed to add a flag allowing to easily override that
|
| |
| |
| |
| | |
change the head to the given commit, which makes the methods more versatile
|
| |
| |
| |
| | |
commit, which possibly dereferences to the respective head
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* refs:
Added notes about git-update-ref
Refs can now set the reference they are pointing to in a controlled fashion by writing their ref file directly
Added TagRefernce creation and deletion including tests
Implemented head methods: create, delete, rename, including tests
refs: added create, delete and rename methods where appropriate. Tests are marked, implementation is needed for most of them
|
| | |
| | |
| | |
| | | |
by writing their ref file directly
|