aboutsummaryrefslogtreecommitdiffhomepage
path: root/README.rst
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2013-09-26 15:54:36 -0400
committerJoey Hess <joey@kitenet.net>2013-09-26 15:54:36 -0400
commitc88fec0bc939c422a1cb44567e7f65418b6edc08 (patch)
tree77af31c0f428447379abb73ce7fbad40f38f7961 /README.rst
parent6a0204ead701904418528fe9c3bf93ae15aa3402 (diff)
parent29ed089ccee73925eb34d35f5ebdfb5706a8d7d7 (diff)
downloadgit-remote-gcrypt-c88fec0bc939c422a1cb44567e7f65418b6edc08.tar.gz
Merge branch 'master' into dgit/sid
Conflicts: git-remote-gcrypt
Diffstat (limited to 'README.rst')
-rw-r--r--README.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.rst b/README.rst
index 3922376..fedd6b0 100644
--- a/README.rst
+++ b/README.rst
@@ -178,8 +178,8 @@ Detecting gcrypt repos
To detect if a git url is a gcrypt repo, use: git-remote-gcrypt --check url
Exit status if 0 if the repo exists and can be decrypted, 1 if the repo
-uses gcrypt but could not be decrypted, and 100 if the repo does not
-exist or could not be accessed.
+uses gcrypt but could not be decrypted, and 100 if the repo is not
+encrypted with gcrypt (or could not be accessed).
Note that this has to fetch the repo contents into the local git
repository, the same as is done when using a gcrypt repo.