delta/python-packages/gitpython.git/test/git/test_repo.py, branch 3.1.2

flattened test folder structure, didn't adjust any file content yet

2010-11-21T18:19:04+00:00

test_submodule: fixed failures that arose due to changes of the original submodule names. Also, a major bug was fixed that cased submodules to always being updated recursively when using the RootModule.update method

2010-11-19T09:28:15+00:00

submodule: previously, it would update the repository configuration during add(), but in fact it must be done during update() when the module is cloned, which is how the git-submodule implementation works

Added test-setup which can test all aspects of the (smart) update method

2010-11-18T10:41:16+00:00

repo: Added create_submodule method which fits into the tradition of offering a create_* method for most important entities.

2010-11-17T20:33:33+00:00

Moved implementation of smart update method to the RootModule implementation, where it may do special things without requiring an interface for everything

Inital implementation of Submodule.move including a very simple and to-be-improved test

2010-11-17T14:24:48+00:00

Optimized test-decorators, by completely removing with_bare_rw_repo, which was mainly copy-paste from with_rw_repo, what a shame

2010-11-15T18:03:53+00:00

Repo: added submodule query and iteration methods similar to the ones provided for Remotes, including test

2010-11-15T17:42:44+00:00

Added python 2.4 support: Repo will now use the original GitCmdObjectDB in python 2.4, as the pure python implementation cannot work without memory maps

2010-07-09T10:18:38+00:00

Adjusted clone method to allow static classmethod clone ( using clone_from ) as well as the previous instance method clone to keep it compatible

2010-07-07T21:45:47+00:00

Fixed small bug in test code

Adjusted previous object creators to use the rev_parse method directly. rev_parse could be adjusted not to return Objects anymore, providing better performance for those who just want a sha only. On the other hand, the method is high-level and should be convenient to use as well, its a starting point for more usually, hence its unlikely to call it in tight loops

2010-07-07T15:30:47+00:00