aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2013-09-19 12:27:15 -0400
committerJoey Hess <joey@kitenet.net>2013-09-19 12:27:15 -0400
commit6ddc0589819f6366d4ffc7b650a4957a040d2979 (patch)
treec1b0cc0634fd868136b30701bb4c4968cd86708a
parent83d519179f5611641802b5de2b5f3f155798f61a (diff)
downloadgit-remote-gcrypt-6ddc0589819f6366d4ffc7b650a4957a040d2979.zip
git-remote-gcrypt-6ddc0589819f6366d4ffc7b650a4957a040d2979.tar.gz
git-remote-gcrypt-6ddc0589819f6366d4ffc7b650a4957a040d2979.tar.bz2
improve docs
-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.