From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.5 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by dcvr.yhbt.net (Postfix) with ESMTP id A62531F54E for ; Mon, 18 Jul 2022 13:30:10 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="IyfQGkqj"; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233794AbiGRN37 (ORCPT ); Mon, 18 Jul 2022 09:29:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54106 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233360AbiGRN3x (ORCPT ); Mon, 18 Jul 2022 09:29:53 -0400 Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 753EE11814 for ; Mon, 18 Jul 2022 06:29:50 -0700 (PDT) Received: by mail-wm1-x334.google.com with SMTP id v67-20020a1cac46000000b003a1888b9d36so9829605wme.0 for ; Mon, 18 Jul 2022 06:29:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=Kk1OlPc4NUzDRxo4DRmVB0qDv0ZN5NGpXJZ+LHYNOOA=; b=IyfQGkqjkRNyjIUSW0InQCbpDIjLgig5+o8yTSuZAO2eZk4+nqad5EwpIfcX05AWH/ /bVek44ZAu4pvqw+3AT0ojRJ1/itOlDk2qRRPtndxFknc9b8VABG76dOacMMRWE1WKv2 QTUZEUcKCwEKB9ZhuQ6s1bInzc3mKWhZbJLzmhDJPsIQOK55dhXJr25qEK5iuJWouUxD RrrnlmEIicLPW7qDPN2WqUVZla8YrFHODDe98qr1U8712cKeNcjwN8dzlzjGOUHNi/XA 1H3JMbZEa4SJfJsyNPWNia/KekwZ93v9fW3p5ehl3vYkiBIDsj+np3MwzSQ0msmlkRMQ R5ug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Kk1OlPc4NUzDRxo4DRmVB0qDv0ZN5NGpXJZ+LHYNOOA=; b=PhREZdDyJGgXUqkJ8KZmus58WblDWsIxirX7QsToUSay7UpMRse/HEeCGwA2DZ3LkA nLKskpBmNk/aRQ6EsgyoN/iKkHtaQa+FXc3YALzXk2n31OawgTzLojS6RZY0jAWauOe7 y4kt0m9YNCOrqP+4wiYCirTIJtifm4G4qIvu1iq0Mm9SavZkBtjFc8/G7RxlXtYf6rN1 TvJY8KhL9jUlrjeQ0Lbo9Ps1lUqksJidYfJgq9rajhi48B2cXTNGC/c6uxdNXIDLXMog SYwUDA2dcS9aEWgRL+CpxcY0OqSL7ZjRrHMLm2zEP+EbEBar2kcKKYNZEkN6H5tcEME+ FlAA== X-Gm-Message-State: AJIora8a0o8MUcoSPOMbZqchnmuU/osF2Zu0sPZ5ystEwNiVnO3Ie16C LCbGnJWEsSmuOtNOf5d9+K4fYpmQpJzi5g== X-Google-Smtp-Source: AGRyM1txDtnjIFvo+vXPaVGE16swMFA/uRGyJNQlUB5Oa3XV4YZan/SdGqZqcYIPw7+o8MNHgOg0ag== X-Received: by 2002:a05:600c:2211:b0:3a3:2149:88e1 with SMTP id z17-20020a05600c221100b003a3214988e1mr204100wml.8.1658150988295; Mon, 18 Jul 2022 06:29:48 -0700 (PDT) Received: from vm.nix.is (vm.nix.is. [2a01:4f8:120:2468::2]) by smtp.gmail.com with ESMTPSA id p4-20020a1c5444000000b003a30572072esm14277296wmi.6.2022.07.18.06.29.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 18 Jul 2022 06:29:47 -0700 (PDT) From: =?UTF-8?q?=C3=86var=20Arnfj=C3=B6r=C3=B0=20Bjarmason?= To: git@vger.kernel.org Cc: Junio C Hamano , Eric Sunshine , Philippe Blain , Derrick Stolee , Taylor Blau , Jeff King , Teng Long , =?UTF-8?q?=C3=86var=20Arnfj=C3=B6r=C3=B0=20Bjarmason?= Subject: [PATCH v4 7/8] docs: move http-protocol docs to man section 5 Date: Mon, 18 Jul 2022 15:29:33 +0200 Message-Id: X-Mailer: git-send-email 2.37.1.1032.gb00b5447790 In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Continue the move of existing Documentation/technical/* protocol and file-format documentation into our main documentation space by moving the http-protocol.txt documentation over. I'm renaming it to "protocol-http" to be consistent with other things in the new gitformat-protocol-* namespace. Signed-off-by: Ævar Arnfjörð Bjarmason --- Documentation/Makefile | 2 +- Documentation/git-upload-pack.txt | 6 ++-- Documentation/gitformat-pack-protocol.txt | 2 +- ...otocol.txt => gitformat-protocol-http.txt} | 29 ++++++++++++++++--- Documentation/gitformat-protocol-v2.txt | 4 +-- command-list.txt | 1 + 6 files changed, 33 insertions(+), 11 deletions(-) rename Documentation/{technical/http-protocol.txt => gitformat-protocol-http.txt} (98%) diff --git a/Documentation/Makefile b/Documentation/Makefile index b4d2361dfc7..44757823e96 100644 --- a/Documentation/Makefile +++ b/Documentation/Makefile @@ -33,6 +33,7 @@ MAN5_TXT += gitformat-pack-protocol.txt MAN5_TXT += gitformat-pack.txt MAN5_TXT += gitformat-protocol-capabilities.txt MAN5_TXT += gitformat-protocol-common.txt +MAN5_TXT += gitformat-protocol-http.txt MAN5_TXT += gitformat-protocol-v2.txt MAN5_TXT += gitformat-signature.txt MAN5_TXT += githooks.txt @@ -107,7 +108,6 @@ TECH_DOCS += SubmittingPatches TECH_DOCS += ToolsForGit TECH_DOCS += technical/bitmap-format TECH_DOCS += technical/hash-function-transition -TECH_DOCS += technical/http-protocol TECH_DOCS += technical/long-running-process-protocol TECH_DOCS += technical/multi-pack-index TECH_DOCS += technical/pack-heuristics diff --git a/Documentation/git-upload-pack.txt b/Documentation/git-upload-pack.txt index 754619222f6..720697df3a0 100644 --- a/Documentation/git-upload-pack.txt +++ b/Documentation/git-upload-pack.txt @@ -39,9 +39,9 @@ OPTIONS --http-backend-info-refs:: Used by linkgit:git-http-backend[1] to serve up `$GIT_URL/info/refs?service=git-upload-pack` requests. See - "Smart Clients" in link:technical/http-protocol.html[the HTTP - transfer protocols] documentation and "HTTP Transport" in the - linkgit:gitformat-protocol-v2[5] documentation. Also understood by + "Smart Clients" in linkgit:gitformat-protocol-http[5] and + "HTTP Transport" in link:technical/protocol-v2.html[the Git + Wire Protocol, Version 2] documentation. Also understood by linkgit:git-receive-pack[1]. :: diff --git a/Documentation/gitformat-pack-protocol.txt b/Documentation/gitformat-pack-protocol.txt index f1bfd6705d9..c82b926e661 100644 --- a/Documentation/gitformat-pack-protocol.txt +++ b/Documentation/gitformat-pack-protocol.txt @@ -17,7 +17,7 @@ Git supports transferring data in packfiles over the ssh://, git://, http:// and file:// transports. There exist two sets of protocols, one for pushing data from a client to a server and another for fetching data from a server to a client. The three transports (ssh, git, file) use the same -protocol to transfer data. http is documented in http-protocol.txt. +protocol to transfer data. http is documented in linkgit:gitformat-protocol-http[5]. The processes invoked in the canonical Git implementation are 'upload-pack' on the server side and 'fetch-pack' on the client side for fetching data; diff --git a/Documentation/technical/http-protocol.txt b/Documentation/gitformat-protocol-http.txt similarity index 98% rename from Documentation/technical/http-protocol.txt rename to Documentation/gitformat-protocol-http.txt index 9d9c7acd512..b85fc86abf6 100644 --- a/Documentation/technical/http-protocol.txt +++ b/Documentation/gitformat-protocol-http.txt @@ -1,5 +1,19 @@ -HTTP transfer protocols -======================= +gitformat-protocol-http(5) +========================== + +NAME +---- +gitformat-protocol-http - Git HTTP-based protocols + + +SYNOPSIS +-------- +[verse] + + + +DESCRIPTION +----------- Git supports two HTTP based transfer protocols. A "dumb" protocol which requires only a standard HTTP server on the server end of the @@ -512,11 +526,18 @@ the id obtained through ref discovery as old_id. TODO: Document this further. - -References +REFERENCES ---------- http://www.ietf.org/rfc/rfc1738.txt[RFC 1738: Uniform Resource Locators (URL)] http://www.ietf.org/rfc/rfc2616.txt[RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1] + +SEE ALSO +-------- + linkgit:gitformat-pack-protocol[5] linkgit:gitformat-protocol-capabilities[5] + +GIT +--- +Part of the linkgit:git[1] suite diff --git a/Documentation/gitformat-protocol-v2.txt b/Documentation/gitformat-protocol-v2.txt index ae4fcc84e37..e29bc4b6a68 100644 --- a/Documentation/gitformat-protocol-v2.txt +++ b/Documentation/gitformat-protocol-v2.txt @@ -54,7 +54,7 @@ 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 used which inevitably sets `GIT_PROTOCOL`. More information can be -found in linkgit:gitformat-pack-protocol[5] and `http-protocol.txt`, as well as the +found in linkgit:gitformat-pack-protocol[5] and linkgit:gitformat-protocol-http[5], as well as the `GIT_PROTOCOL` definition in `git.txt`. In all cases the response from the server is the capability advertisement. @@ -78,7 +78,7 @@ 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 +info/refs request as described in linkgit:gitformat-protocol-http[5] and requests that v2 be used by supplying "version=2" in the `Git-Protocol` header. C: GET $GIT_URL/info/refs?service=git-upload-pack HTTP/1.0 diff --git a/command-list.txt b/command-list.txt index c364557fe09..c87b07e779c 100644 --- a/command-list.txt +++ b/command-list.txt @@ -217,6 +217,7 @@ gitformat-pack-cruft gitformats gitformat-pack-protocol gitformats gitformat-protocol-capabilities gitformats gitformat-protocol-common gitformats +gitformat-protocol-http gitformats gitformat-protocol-v2 gitformats gitformat-signature gitformats gitglossary guide -- 2.37.1.1032.gb00b5447790