From: Jonathan Tan Date: Tue, 09 Apr 2019 20:31:32 GMT Subject: [PATCH v2 0/2] Server options when cloning Message-ID: In-Reply-To: <20190405204413.93900-1-jonathantanmy@google.com> I created v2 by rewriting jt/clone-server-option, so you'll see some Reviewed-by lines and Signed-off-by lines with another name than mine. Changes from v1: - Broke long line. (DUP->NODUP was already done by Junio in jt/clone-server-option, so you don't see it in the range-diff below.) - Warn if server-option is specified but not sent to the server (in fetch and clone). - Document that server's handling of server-option is server-specific. These patches are on maint, matching jt/clone-server-option, but should apply cleanly on master too. Jonathan Tan (2): transport: warn if server options are unsupported clone: send server options when using protocol v2 Documentation/fetch-options.txt | 3 ++- Documentation/git-clone.txt | 8 +++++++ builtin/clone.c | 6 ++++++ t/t5702-protocol-v2.sh | 38 +++++++++++++++++++++++++++++++++ transport.c | 8 +++++++ 5 files changed, 62 insertions(+), 1 deletion(-) Range-diff against v1: -: ---------- > 1: af3cc05324 transport: warn if server options are unsupported 1: 90ce94e039 ! 2: 142c25abd2 clone: send server options when using protocol v2 @@ -11,10 +11,27 @@ 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. + 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 + --- a/Documentation/fetch-options.txt + +++ b/Documentation/fetch-options.txt +@@ + --server-option=