[PATCH 1/7] Documentation/git-push.txt: Document when --signed may fail
- From
Dave Borowitz <dborowitz@google.com>
- Date
- Aug 13, 2015, 19:00 UTC
- Message-ID
- <1439492451-11233-2-git-send-email-dborowitz@google.com>
- In-Reply-To
- <1439492451-11233-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 <dborowitz@google.com> --- 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..f8b8b8b 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 `gpg` executable is not available, + 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