From: Jonathan Tan Date: Fri, 12 Apr 2019 19:51:22 +0000 (-0700) Subject: clone: send server options when using protocol v2 X-Git-Tag: v2.22.0-rc0~23^2 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=6e98305985555ced61971ca0170dd976554193c0;p=thirdparty%2Fgit.git clone: send server options when using protocol v2 Commit 5e3548ef16 ("fetch: send server options when using protocol v2", 2018-04-24) taught "fetch" the ability to send server options when using protocol v2, but not "clone". This ability is triggered by "-o" or "--server-option". Teach "clone" the same ability, except that because "clone" already has "-o" for another parameter, teach "clone" only to receive "--server-option". Explain in the documentation, both for clone and for fetch, that server handling of server options are server-specific. This is similar to receive-pack's handling of push options - currently, they are just sent to hooks to interpret as they see fit. Signed-off-by: Jonathan Tan Reviewed-by: Jonathan Nieder Signed-off-by: Junio C Hamano --- diff --git a/Documentation/fetch-options.txt b/Documentation/fetch-options.txt index fa0a3151b3..91c47752ec 100644 --- a/Documentation/fetch-options.txt +++ b/Documentation/fetch-options.txt @@ -216,7 +216,8 @@ endif::git-pull[] --server-option=