diff options
| author | Sebastian Thiel <byronimo@gmail.com> | 2009-10-26 10:57:11 +0100 |
|---|---|---|
| committer | Sebastian Thiel <byronimo@gmail.com> | 2009-10-26 10:57:11 +0100 |
| commit | 9dfd6bcca5499e1cd472c092bc58426e9b72cccc (patch) | |
| tree | 12f2418d0843460d1d51c346dd35325fabc12a09 /TODO | |
| parent | f9cec00938d9059882bb8eabdaf2f775943e00e5 (diff) | |
| parent | 44a601a068f4f543f73fd9c49e264c931b1e1652 (diff) | |
| download | gitpython-9dfd6bcca5499e1cd472c092bc58426e9b72cccc.tar.gz | |
Merge branch 'refs' into index
* 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
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 19 |
1 files changed, 9 insertions, 10 deletions
@@ -87,22 +87,21 @@ Refs ----- * When adjusting the reference of a symbolic reference, the ref log might need adjustments as well. This is not critical, but would make things totally 'right' -* Reference Objects should be able to set the commit they are pointing to, making - the commit property read-write. Tags are a special case of this and would need - to be handled as well ! -* Ability to create new heads and tags in the Repository ( but using the respective - Reference Type ), i.e. Head.create(repo, name, commit = 'HEAD') or - TagReference.create(repo, name -* Ability to rename references and tags -* Ability to remove references and tags -* Ability to checkout a reference - -* Check whether we are the active reference HEAD.commit == self.commit + - same with adjusting references directly + !! - Could simply rewrite it using git-update-ref which works nicely for symbolic + and for normal refs !! +* Check whether we are the active reference HEAD.reference == this_ref + - NO: The reference dosnt need to know - in fact it does not know about the + main HEAD, so it may not use it. This is to be done in client code only. + Remove me Remote ------ * 'push' method needs a test, a true test repository is required though, a fork of a fork would do :)! * Fetch should return heads that where updated, pull as well. +* Creation and deletion methods for references should be part of the interface, allowing + repo.create_head(...) instaed of Head.create(repo, ...). Its a convenience thing, clearly Repo ---- |