From: Dave Borowitz Date: Wed, 19 Aug 2015 15:26:39 GMT Subject: [PATCH v2 1/9] Documentation/git-push.txt: Document when --signed may fail Message-ID: <1439998007-28719-2-git-send-email-dborowitz@google.com> In-Reply-To: <1439998007-28719-1-git-send-email-dborowitz@google.com> Like --atomic, --signed will fail if the server does not advertise the necessary capability. In addition, it requires gpg on the client side. Signed-off-by: Dave Borowitz --- Documentation/git-push.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt index 135d810..da0a98d 100644 --- a/Documentation/git-push.txt +++ b/Documentation/git-push.txt @@ -137,7 +137,9 @@ already exists on the remote side. GPG-sign the push request to update refs on the receiving side, to allow it to be checked by the hooks and/or be logged. See linkgit:git-receive-pack[1] for the details - on the receiving end. + on the receiving end. If the attempt to sign with `gpg` fails, + or if the server does not support signed pushes, the push will + fail. --[no-]atomic:: Use an atomic transaction on the remote side if available. -- 2.5.0.276.gf5e568e