Simply detect if using git repository backend. gitception:// is unneeded

Simply treat absolute paths that do not lead to a HEAD file as local
directory backends, and all other as git backends.

1 files changed, 11 insertions, 3 deletions

diff --git a/README.rst b/README.rst
index 7e48b97..8b84d0e 100644
--- a/README.rst
+++ b/README.rst
@@ -16,9 +16,10 @@ Remote helper programs are invoked by git to handle network transport.
 This helper handles gcrypt:: URLs that will access a remote repository
 encrypted with GPG, using our custom format.
 
-Supported locations are `local`, `ssh://`, `sftp://` and
-`gitception://`. `gcrypt::gitception://<giturl>` allows stacking gcrypt
-on top of any other git transport.
+Supported locations are `local`, `ssh://` and `sftp://`, where the
+repository is stored as a set of files. If the location instead is any
+`<giturl>`, gcrypt will store the same representation in a git
+repository, and so it can be bridged over any git transport.
 
 .. NOTE:: Repository format MAY STILL change, incompatibly
 
@@ -91,6 +92,13 @@ Examples
     git remote add cryptremote  gcrypt::ssh://example.com:repo
     git push cryptremote HEAD
 
+How to use a git backend::
+
+    # notice that the target repo must already exist and its
+    # `master` branch will be overwritten!
+    git remote add gitcrypt gcrypt::git@example.com:repo
+    git push gitcrypt HEAD
+
 Notes
 =====