diff options
author | Ulrike Uhlig <u@451f.org> | 2018-07-24 11:29:18 +0200 |
---|---|---|
committer | Sean Whitton <spwhitton@spwhitton.name> | 2018-07-24 18:20:02 +0800 |
commit | c66b318c8a30edfc0dd489542724e2e9add806e6 (patch) | |
tree | b42234748fe43f206d0964b0773f072faa6f3fcc | |
parent | 321550f68e03555ec953b7a4be3974ade70ba1a9 (diff) | |
download | git-remote-gcrypt-c66b318c8a30edfc0dd489542724e2e9add806e6.tar.gz |
Document connectivity issue error message
Sometimes, git-remote-gcrypt reports 'gcrypt: Repository not found', but
this can be due to all sorts of connectivity issues, or even due to
ssh-agent using a wrong identity. This should at least be in the docs as
it is a very unprecise error message.
Signed-off-by: Ulrike Uhlig <ulrike@debian.org>
-rw-r--r-- | README.rst | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -239,6 +239,9 @@ 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 +authentication, port, or network connectivity issues. + See also ======== |