From: Dave Borowitz Date: Wed, 19 Aug 2015 15:26:39 +0000 (-0400) Subject: Documentation/git-push.txt: document when --signed may fail X-Git-Tag: v2.6.0-rc0~18^2~8 X-Git-Url: https://git.lorimer.id.au/gitweb.git/diff_plain/f9e0952d1ff1c1f5c8fbbe9d914bb30012341a04?ds=inline;hp=--cc Documentation/git-push.txt: document when --signed may fail 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 Signed-off-by: Junio C Hamano --- f9e0952d1ff1c1f5c8fbbe9d914bb30012341a04 diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt index 135d810b7a..da0a98d58c 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.