summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorSebastian Thiel <byronimo@gmail.com>2014-11-19 16:38:12 +0100
committerSebastian Thiel <byronimo@gmail.com>2014-11-19 16:38:12 +0100
commit616ae503462ea93326fa459034f517a4dd0cc1d1 (patch)
tree99b6c9ecbef6e9b09bce2537b0a068073169ce94 /doc
parent0f54c8919f297a5e5c34517d9fed0666c9d8aa10 (diff)
downloadgitpython-616ae503462ea93326fa459034f517a4dd0cc1d1.tar.gz
Fixes #122
For now, referencing github directly seems to be safest.
Diffstat (limited to 'doc')
-rw-r--r--doc/source/whatsnew.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/source/whatsnew.rst b/doc/source/whatsnew.rst
index 7a5ef53d..f71d88e6 100644
--- a/doc/source/whatsnew.rst
+++ b/doc/source/whatsnew.rst
@@ -52,7 +52,7 @@ Guided Upgrade
**************
This guide should help to make the upgrade as painless as possible, hence it points out where to start, and what to look out for.
-* Have a look at the CHANGES log file and read all important changes about 0.3 for an overview.
+* Have a look at https://github.com/gitpython-developers/GitPython/blob/0.3/doc/source/changes.rst
* Start applying the renames, generally the ``utils`` modules are now called ``util``, ``errors`` is called ``exc``.
* Search for occurrences of the ``sha`` property of object instances. A similar value can be obtained through the new ``hexsha`` property. The native sha1 value is the ``binsha`` though.
* Search for code which instantiates objects directly. Their initializer now requires a 20 byte binary Sha1, rev-specs cannot be used anymore. For a similar effect, either convert your hexadecimal shas to binary shas beforehand ( ``binascii.unhexlify`` for instance ), or use higher level functions such as ``Object.new``, ``Repo.commit`` or ``Repo.tree``. The latter ones takes rev-specs and hexadecimal sha1 hashes.