| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
on lighthouse.
README/intro.rst: added information about the new repository at github
tree: added marker to indicate that submodules would have to be returned there
|
|
|
|
|
| |
TODO: Added info about doc improvements
Authors: Added myself as Contributor, and noted the partial rewrite which happend in 0.2
|
| |
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
| |
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
|
|
|
|
| |
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
|
|
|
|
| |
studied, but they would be hard to 'produce'
|
| |
|
|
|
|
| |
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
|
|
|
|
| |
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
|
|
|
|
|
|
| |
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
|
|
|
|
| |
reference paths
|
|
|
|
| |
expected. Plenty of cases still to be tested
|
|
|
|
| |
index.checkout: added simple method allowing to checkout files from the index, including simple test
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
* 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
|
| | |
|
| |
| |
| |
| | |
required to have a nice API. Tests are not yet fully done either
|
|/ |
|
| |
|
|
|
|
| |
TODO list
|
|
|
|
|
|
| |
controlled, including test.
Added commit method which will return the commit for detached symbolic refs or for normal symbolic refs which is quite convenient
|
| |
|
|
|
|
|
|
|
|
| |
types of references and allow special handling
Head.reset now is an instance method of HEAD type
Concatenated all reference specific tests into test_refs
started to fix tests breaking now because of changed interface
|
|
|
|
|
|
|
| |
other items as well as the working tree
Diff.Diffable: added callback allowing superclasses to preprocess diff arguments
Diff.Diff: added eq, ne and hash methods, string methods would be nice
|
|
|
|
| |
nature of the command. Yet I don't really like the way you have to call it as repo has to be ṕassed as first arg
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* index:
Removed index test marker for custom commits as this boils down to a good way to add files to the index/remove them and make commits which are possibly customized with custom parents
index writing now creates a sha on the content making it possible to write valid indices after manually removing or altering entriesgst
Implemented merge/resolve handling , but realized that index writing is not yet working properly as it is sha1 checked as well. This explains what my 20 byte 'extension_data' actually is ;)
index: Added write_tree method including test
index.iter_blobs method added including tests ( which have been improved generally for more coverage )
tree.traverse: Added prune functionality - previously the predciate did both, pruning and preventing to return items
Improved testing of index against trees, tests succeed with next commit
Initial version of merge including tests for one-way, two-way and tree-way merge
index writing added including simple test, improved docs of IndexEntry
improved IndexEntry type and added test for parsing of the stage
Improved tuple access of EntryIndex class including test, stage and type access still needs to be decoded though
Added initial version of the index reading from file - IndexEntry interface is to be improved though, writing needs to be implemented as well
Added frame for index implementation and testing
|
| | |
|
| | |
|
| |
| |
| |
| | |
access still needs to be decoded though
|
| | |
|
| |
| |
| |
| | |
directly.Considering the implementation of the git commnd which temporarily keeps it in a cache, it doesnt make a huge diffence as the data is kept in memory while streaming. Only good thing is that it is in a different process so python will never see it if done properly
|
| |
| |
| |
| | |
operations more convenient, like repo.remotes.origin.fetch
|
|/
|
|
| |
would compare HEAD against the working tree, not the index which was intended
|
|
|
|
| |
tests bare the risk that things do not work properly outside of the sandbox.
|
|
|
|
|
|
| |
and to be more efficient of course ;)
TODO: Added info about possible config improvement
|
| |
|
|
|
|
|
|
| |
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
|
|
here and there ;)
|