aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2018-07-24 18:25:16 +0800
committerSean Whitton <spwhitton@spwhitton.name>2018-07-24 18:25:31 +0800
commita9b8367618fd6d0f039ecb6d8ac9e3f504102c52 (patch)
tree1e6679da61ca992cf9deadfb01db6d767fa34cbb
parentc66b318c8a30edfc0dd489542724e2e9add806e6 (diff)
downloadgit-remote-gcrypt-a9b8367618fd6d0f039ecb6d8ac9e3f504102c52.tar.gz
tweak wording in Ulrike's patch
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
-rw-r--r--README.rst3
1 files changed, 2 insertions, 1 deletions
diff --git a/README.rst b/README.rst
index 3b9d7ec..46457a4 100644
--- a/README.rst
+++ b/README.rst
@@ -239,7 +239,8 @@ which means that your push can suddenly take significantly longer than
you were expecting, as your whole history has to be reuploaded.
This push might fail over a poor link.
-git-remote-gcrypt might report a repository as not found when having
+git-remote-gcrypt might report a repository as "not found" when the
+repository does in fact exist, but git-remote-gcrypt is having
authentication, port, or network connectivity issues.
See also