From patchwork Sun Mar 24 15:52:17 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: =?utf-8?q?SZEDER_G=C3=A1bor?= X-Patchwork-Id: 10867503 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 7098914DE for ; Sun, 24 Mar 2019 15:52:38 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 5526E2930E for ; Sun, 24 Mar 2019 15:52:38 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 422BA29436; Sun, 24 Mar 2019 15:52:38 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.0 required=2.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id CC2862930E for ; Sun, 24 Mar 2019 15:52:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726889AbfCXPw0 (ORCPT ); Sun, 24 Mar 2019 11:52:26 -0400 Received: from mail-wr1-f68.google.com ([209.85.221.68]:38722 "EHLO mail-wr1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726603AbfCXPw0 (ORCPT ); Sun, 24 Mar 2019 11:52:26 -0400 Received: by mail-wr1-f68.google.com with SMTP id g12so7345573wrm.5 for ; Sun, 24 Mar 2019 08:52:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=pW4+v+x/bsdUq1YfedztakDhpmLT5SUJT8/Oto3vApU=; b=vgnhPC2DFw5nXMsSNosGeP5zrYZnoA6SPE63Ma93XFzrqowAfK9OLoK5lkmn60xgxh Yo3z7lSliCRCLxX1aMiPfYiOt+F6b1OENLrvKJ0Day3qN8rx1bpLS837GHA9CJciPgvB rdSi7GNLnOClfg7ues7QOVtQ2h3HgDCY13ibpcK9LoEdGKPYg8Ye7IJ1UwjKB+AALcXX w9OHmRC0u3KEFt6BD6zD1x681St9xyTfiPVwZQ0sZDGytNoRK4YVJb3PRtFS3vqgpsXt u+X1HDRnkNhZ3OoFQeBEi/2G5YC9RSWT3kwD34SCut26bOrmznamImhJvT0Xl0J1jNWM Puwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=pW4+v+x/bsdUq1YfedztakDhpmLT5SUJT8/Oto3vApU=; b=eTFQZ8ZE4VJxO+/Skk5zwFoKJ+ZykfAjztedTPbvoPhaqyaXpeUSSG8DCeTRjgKYoq pgw1MR4TGPwCCIHFsjO25Dfwhr9j+vz2/jIuK7Yk6O4ySPuBHxsurgynQJ4AaONc+67A 6ku5D1NzXEge5LH3PnqVjoBVgj2XCqKb+m/vkD755T4lD881Gz4jtfGxnLWrLkuI3h6f au06DI3GEd6SZygl1Nq6lfVvQ503aAKuUAvWWJAohK9sLa7H0JPg5EjUKUuqlEt15Eg+ dPx947UMRihftgdnCCNdviMXhd9UzLUhjg6jkCcU2YR1FjBM1thuMUzStcc9Alxhizr5 MVvQ== X-Gm-Message-State: APjAAAUIl9qhQFCmsSG+/1owQmqzeXQp1KDAmPVJKqcihP8KyTDhZ1Wg fANN9JRtFnts2QUnEG2J37n92CW8 X-Google-Smtp-Source: APXvYqzXyVLrgg0Ar6Gb6OAvpR6jrb1W8eZ3hYJTsz+MQWCxwVdfmlDKl2Xl9w1Z64V8SsgO8JoMVg== X-Received: by 2002:adf:c7c8:: with SMTP id y8mr13965481wrg.149.1553442743930; Sun, 24 Mar 2019 08:52:23 -0700 (PDT) Received: from localhost.localdomain (x4d0c479e.dyn.telefonica.de. [77.12.71.158]) by smtp.gmail.com with ESMTPSA id y1sm31197407wrd.34.2019.03.24.08.52.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 24 Mar 2019 08:52:22 -0700 (PDT) From: =?utf-8?q?SZEDER_G=C3=A1bor?= To: git@vger.kernel.org Cc: =?utf-8?q?SZEDER_G=C3=A1bor?= Subject: [PATCH 1/3] Documentation/git-diff-tree.txt: fix formatting Date: Sun, 24 Mar 2019 16:52:17 +0100 Message-Id: <20190324155219.2284-1-szeder.dev@gmail.com> X-Mailer: git-send-email 2.21.0.539.g07239c3a71.dirty MIME-Version: 1.0 Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Some more recent versions of Asciidoctor issue the following warning while building the documentation: ASCIIDOC git-diff-tree.xml asciidoctor: WARNING: diff-format.txt: line 2: unterminated listing block This highlights an issue where the "Raw output format" header is not rendered as a header, and the rest of the document is rendered in monospace. This is not caused by 'diff-format.txt' in itself, but rather by 'git-diff-tree.txt' including 'pretty-formats.txt' and 'diff-format.txt' on subsequent lines, while the former happens to end with monospace-formatted example commands. Fix this by inserting an empty line between the two include:: directives. The page rendered with AsciiDoc doesn't have this formatting issue. Signed-off-by: SZEDER Gábor --- Documentation/git-diff-tree.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/git-diff-tree.txt b/Documentation/git-diff-tree.txt index 24f32e8c54..5c8a2a5e97 100644 --- a/Documentation/git-diff-tree.txt +++ b/Documentation/git-diff-tree.txt @@ -118,6 +118,7 @@ include::pretty-options.txt[] include::pretty-formats.txt[] + include::diff-format.txt[] GIT From patchwork Sun Mar 24 21:55:30 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: =?utf-8?q?SZEDER_G=C3=A1bor?= X-Patchwork-Id: 10867745 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id C6B2B17EF for ; Sun, 24 Mar 2019 21:55:55 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id AFFD92923D for ; Sun, 24 Mar 2019 21:55:55 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id A37D229258; Sun, 24 Mar 2019 21:55:55 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.0 required=2.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 36AC02923D for ; Sun, 24 Mar 2019 21:55:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728963AbfCXVzw (ORCPT ); Sun, 24 Mar 2019 17:55:52 -0400 Received: from mail-wr1-f68.google.com ([209.85.221.68]:35059 "EHLO mail-wr1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726317AbfCXVzv (ORCPT ); Sun, 24 Mar 2019 17:55:51 -0400 Received: by mail-wr1-f68.google.com with SMTP id w1so7966859wrp.2 for ; Sun, 24 Mar 2019 14:55:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=aosOI7X8jOegorDWKC5cBD8GjBzQO0+hNli2kaJQGcg=; b=NgUM2pJEY8J0oAf6ku7pfh73X7al59/+MM5peR/hbvDdCxlLvj+8LFm5rdqQrSCMgr diYTnfrx/jKG8D05w8OhKKrnnKjpUJjY11+AxIA1cf7k2M6l1As+lIdWV7MBmIbteHrd zxQPo8WZvhp5HQlJ1OyURh8KMAD0NopA91i9iMK+1LcjDDxgRMg784gl2rOfJ1VkUN20 j32zh9E86wwBoz2JITVFavXez6RQHWgYTxS7bRdTZGlkB8AXR5iQH4GRrGSSC+9W12IQ CdDX8K+gHZX8kGQcIuqm8nHXwz/Rl0NSQJxPM1iv6glk0fv++miRZuODtUd7aci4QW7i fQEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=aosOI7X8jOegorDWKC5cBD8GjBzQO0+hNli2kaJQGcg=; b=DarBkBoRhH35hEMPX8TerUrTQW0UWR0PQYUNXD/XH7lxNuMP8DnxtJRy/fXMhZs4Na 4yOmOz26B6x37kSVe6dQSPF/w1Z6aSIvWtnvL2QanQBsMXiy/5HCE+I/G6eRGymDcprs CKk2V0aLQTAwMrOzBDxhtcL2/sJ0kRdEVOmyAMm1pVoYDOsjw4YLZ7j23yyhCakqk/9q Xujv1zK5nrEPsnr8OfGBzx6s6X+J9T/0/9aG8yBGjl3VsrufBwSWnyymtYK7lK575PCO zqfb++riJ8kapz0/BpuQklfTEYhUnzhviBOvCWgic4t6fS+jw2PjpDhm7ynODFwOVqXI 5qLA== X-Gm-Message-State: APjAAAW28rpxuMXf2tCrTGd3sEoDj+Som5d0tDypSp8xuqHWKbJUgkGV uc97nN0ghIdlgrAIog327ksiCuPa X-Google-Smtp-Source: APXvYqxf92w870WlXOa4XHH6muKMxwsRbLj6c3qcHmFWt/tS9SgvMZxkgQ0FP0IxZ2lSob5zjWf/pg== X-Received: by 2002:a5d:4987:: with SMTP id r7mr13022556wrq.280.1553464549428; Sun, 24 Mar 2019 14:55:49 -0700 (PDT) Received: from localhost.localdomain (x4d0c479e.dyn.telefonica.de. [77.12.71.158]) by smtp.gmail.com with ESMTPSA id o17sm15023530wrw.73.2019.03.24.14.55.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 24 Mar 2019 14:55:48 -0700 (PDT) From: =?utf-8?q?SZEDER_G=C3=A1bor?= To: git@vger.kernel.org Cc: Jeff King , Todd Zullinger , =?utf-8?q?Mar?= =?utf-8?q?tin_=C3=85gren?= , "brian m. carlson" , Johannes Schindelin , Junio C Hamano , =?utf-8?q?SZEDER_G=C3=A1bor?= Subject: [PATCH v2 2/6] Documentation/technical/api-config.txt: fix formatting Date: Sun, 24 Mar 2019 22:55:30 +0100 Message-Id: <20190324215534.9495-3-szeder.dev@gmail.com> X-Mailer: git-send-email 2.21.0.539.g07239c3a71.dirty In-Reply-To: <20190324215534.9495-1-szeder.dev@gmail.com> References: <20190324155219.2284-1-szeder.dev@gmail.com> <20190324215534.9495-1-szeder.dev@gmail.com> MIME-Version: 1.0 Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Asciidoctor versions v1.5.7 or later print the following warning while building the documentation: ASCIIDOC technical/api-config.html asciidoctor: WARNING: api-config.txt: line 232: unterminated listing block This highlight an issue (even with older Asciidoctor versions) where the length of the '----' lines surrounding a code example don't match, and the rest of the document is rendered in monospace. Fix this by making sure that the length of those lines match. The page rendered with AsciiDoc doesn't have this formatting issue. Signed-off-by: SZEDER Gábor --- Documentation/technical/api-config.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/technical/api-config.txt b/Documentation/technical/api-config.txt index fa39ac9d71..7d20716c32 100644 --- a/Documentation/technical/api-config.txt +++ b/Documentation/technical/api-config.txt @@ -229,7 +229,7 @@ A `config_set` can be used to construct an in-memory cache for config-like files that the caller specifies (i.e., files like `.gitmodules`, `~/.gitconfig` etc.). For example, ---------------------------------------- +---------------------------------------- struct config_set gm_config; git_configset_init(&gm_config); int b; From patchwork Sun Mar 24 15:52:19 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: =?utf-8?q?SZEDER_G=C3=A1bor?= X-Patchwork-Id: 10867507 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id DC69F18B7 for ; Sun, 24 Mar 2019 15:52:38 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id C81032930E for ; Sun, 24 Mar 2019 15:52:38 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id BB94F2942F; Sun, 24 Mar 2019 15:52:38 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.0 required=2.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 18DCE29433 for ; Sun, 24 Mar 2019 15:52:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727737AbfCXPwa (ORCPT ); Sun, 24 Mar 2019 11:52:30 -0400 Received: from mail-wm1-f68.google.com ([209.85.128.68]:33376 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726603AbfCXPwa (ORCPT ); Sun, 24 Mar 2019 11:52:30 -0400 Received: by mail-wm1-f68.google.com with SMTP id z6so7805746wmi.0 for ; Sun, 24 Mar 2019 08:52:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=8ooSqNOfjz+2CajgdxK5nnponc6MrVlTnMs4bRNcJT8=; b=QtjNjpKvgTBuc4nxNgaM0108Q0JB2KzbRYDlh6CmFZPViD+L7bO65QtiocCO/ChcHg g/hlZ5X93pUJJoy8t/Tuf9ggIMA1R34fpifOmDJqwFNrDY6cSUEBwkpmXW9h00e57lnG vXTB85V74Ojd81MZKUH0yxKKe1CiNse/IdOfCJAzFMpDKkO4+BzC5LmKqbxcPHh8h3Hz 7gXc4JqwmhIKHNlET89I+DqCFoGNNA7ycOhlJMLvw2ve/e/xTQnOJ7b5XXznwBW6T/N9 YiPHhMyZ4StIdVweWZJpUv92pif85NBmKsF8QR51BmrmQAE9b6ucN9dzJi3l0+BE1W9X mYRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=8ooSqNOfjz+2CajgdxK5nnponc6MrVlTnMs4bRNcJT8=; b=j+UBaMTAN67mdr7VvBmfBVxEhJe/j35Eq9DbT0GHAdIWNtosZqvRp31WMJcd4MPUTh iG6RXF+ivipNH8L2iabxg1Y5fHltpLXZuDoD86qeRyItgqi2kbHL0sAOi+fKKqTcNR3m nTxFQ4ZxnCQ48qC+90DWsr9PKBfppjWjKJF+cIJW1CQqIom12SYnrBdUnp0qBzwf/WUd i1tvGC/5KTQQpalQUCle3QeNl292dmESszLhjtbEesVreiiddVMX/+4GOOtk5YMrCpQ9 dnEYGXj7fef7T64EhLjGgWCRQ8YNIdyN753CttvKFNmgijkud2TXgzGjBmqoeq3pk0vK Afrg== X-Gm-Message-State: APjAAAW0X253jDqx4lsY2baB9vrA3Ugs9YHKOZg4sPfNd94SblVqDfS3 if4I+R7SzafYjDPGl5uy71t7k626 X-Google-Smtp-Source: APXvYqxxuW/HkQcY+aQsaNtCQEA/sR3JHYywTUoEWsSHBBHKXGLJEoSWGqgr9lavhsMrrFMDOPxG2A== X-Received: by 2002:a05:600c:2293:: with SMTP id 19mr2751075wmf.77.1553442748367; Sun, 24 Mar 2019 08:52:28 -0700 (PDT) Received: from localhost.localdomain (x4d0c479e.dyn.telefonica.de. [77.12.71.158]) by smtp.gmail.com with ESMTPSA id y1sm31197407wrd.34.2019.03.24.08.52.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 24 Mar 2019 08:52:27 -0700 (PDT) From: =?utf-8?q?SZEDER_G=C3=A1bor?= To: git@vger.kernel.org Cc: =?utf-8?q?SZEDER_G=C3=A1bor?= Subject: [PATCH 3/3] Documentation/technical/protocol-v2.txt: fix formatting Date: Sun, 24 Mar 2019 16:52:19 +0100 Message-Id: <20190324155219.2284-3-szeder.dev@gmail.com> X-Mailer: git-send-email 2.21.0.539.g07239c3a71.dirty In-Reply-To: <20190324155219.2284-1-szeder.dev@gmail.com> References: <20190324155219.2284-1-szeder.dev@gmail.com> MIME-Version: 1.0 Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Some more recent versions of Asciidoctor issue the following warning while building the documentation: ASCIIDOC technical/protocol-v2.html asciidoctor: WARNING: protocol-v2.txt: line 38: unterminated listing block This highlights an issue where the 'Initial Client Request' header is not rendered as a header but in monospace. I'm not sure what exactly causes this issue and why it's an issue only with this particular header, but all headers in 'protocol-v2.txt' are written like this: Initial Client Request ------------------------ i.e. the header itself is indented by a space, and the "underline" Dropping that indentation and making the length of the underline match the length of the header apparently fixes this issue. While at it, adjust all other headers 'protocol-v2.txt' as well, to match the style we use everywhere else. The page rendered with AsciiDoc doesn't have this formatting issue. Signed-off-by: SZEDER Gábor --- Documentation/technical/protocol-v2.txt | 52 ++++++++++++------------- 1 file changed, 26 insertions(+), 26 deletions(-) diff --git a/Documentation/technical/protocol-v2.txt b/Documentation/technical/protocol-v2.txt index ead85ce35c..03264c7d9a 100644 --- a/Documentation/technical/protocol-v2.txt +++ b/Documentation/technical/protocol-v2.txt @@ -1,5 +1,5 @@ - Git Wire Protocol, Version 2 -============================== +Git Wire Protocol, Version 2 +============================ This document presents a specification for a version 2 of Git's wire protocol. Protocol v2 will improve upon v1 in the following ways: @@ -22,8 +22,8 @@ will be commands which a client can request be executed. Once a command has completed, a client can reuse the connection and request that other commands be executed. - Packet-Line Framing ---------------------- +Packet-Line Framing +------------------- All communication is done using packet-line framing, just as in v1. See `Documentation/technical/pack-protocol.txt` and @@ -34,8 +34,8 @@ In protocol v2 these special packets will have the following semantics: * '0000' Flush Packet (flush-pkt) - indicates the end of a message * '0001' Delimiter Packet (delim-pkt) - separates sections of a message - Initial Client Request ------------------------- +Initial Client Request +---------------------- In general a client can request to speak protocol v2 by sending `version=2` through the respective side-channel for the transport being @@ -43,22 +43,22 @@ used which inevitably sets `GIT_PROTOCOL`. More information can be found in `pack-protocol.txt` and `http-protocol.txt`. In all cases the response from the server is the capability advertisement. - Git Transport -~~~~~~~~~~~~~~~ +Git Transport +~~~~~~~~~~~~~ When using the git:// transport, you can request to use protocol v2 by sending "version=2" as an extra parameter: 003egit-upload-pack /project.git\0host=myserver.com\0\0version=2\0 - SSH and File Transport -~~~~~~~~~~~~~~~~~~~~~~~~ +SSH and File Transport +~~~~~~~~~~~~~~~~~~~~~~ When using either the ssh:// or file:// transport, the GIT_PROTOCOL environment variable must be set explicitly to include "version=2". - HTTP Transport -~~~~~~~~~~~~~~~~ +HTTP Transport +~~~~~~~~~~~~~~ When using the http:// or https:// transport a client makes a "smart" info/refs request as described in `http-protocol.txt` and requests that @@ -79,8 +79,8 @@ A v2 server would reply: Subsequent requests are then made directly to the service `$GIT_URL/git-upload-pack`. (This works the same for git-receive-pack). - Capability Advertisement --------------------------- +Capability Advertisement +------------------------ A server which decides to communicate (based on a request from a client) using protocol version 2, notifies the client by sending a version string @@ -101,8 +101,8 @@ to be executed by the client. key = 1*(ALPHA | DIGIT | "-_") value = 1*(ALPHA | DIGIT | " -_.,?\/{}[]()<>!@#$%^&*+=:;") - Command Request ------------------ +Command Request +--------------- After receiving the capability advertisement, a client can then issue a request to select the command it wants with any particular capabilities @@ -137,8 +137,8 @@ command be executed or can terminate the connection. A client may optionally send an empty request consisting of just a flush-pkt to indicate that no more requests will be made. - Capabilities --------------- +Capabilities +------------ There are two different types of capabilities: normal capabilities, which can be used to to convey information or alter the behavior of a @@ -153,8 +153,8 @@ management on the server side in order to function correctly. This permits simple round-robin load-balancing on the server side, without needing to worry about state management. - agent -~~~~~~~ +agent +~~~~~ The server can advertise the `agent` capability with a value `X` (in the form `agent=X`) to notify the client that the server is running version @@ -168,8 +168,8 @@ printable ASCII characters except space (i.e., the byte range 32 < x < and debugging purposes, and MUST NOT be used to programmatically assume the presence or absence of particular features. - ls-refs -~~~~~~~~~ +ls-refs +~~~~~~~ `ls-refs` is the command used to request a reference advertisement in v2. Unlike the current reference advertisement, ls-refs takes in arguments @@ -199,8 +199,8 @@ The output of ls-refs is as follows: symref = "symref-target:" symref-target peeled = "peeled:" obj-id - fetch -~~~~~~~ +fetch +~~~~~ `fetch` is the command used to fetch a packfile in v2. It can be looked at as a modified version of the v1 fetch where the ref-advertisement is @@ -444,8 +444,8 @@ header. 2 - progress messages 3 - fatal error message just before stream aborts - server-option -~~~~~~~~~~~~~~~ +server-option +~~~~~~~~~~~~~ If advertised, indicates that any number of server specific options can be included in a request. This is done by sending each option as a