All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Philippe Blain <levraiphilippeblain@gmail.com>
Subject: Re: [PATCH] Docs: web server must setenv GIT_PROTOCOL for v2
Date: Fri, 10 Sep 2021 10:02:33 -0400	[thread overview]
Message-ID: <YTtleYs48A1NpUpp@coredump.intra.peff.net> (raw)
In-Reply-To: <YTtECuP2/A6+EI4J@coredump.intra.peff.net>

On Fri, Sep 10, 2021 at 07:39:54AM -0400, Jeff King wrote:

> I'll re-roll with that change, plus some documentation changes adapted
> to this new approach.

Here's what I came up with. I think this should replace both
jk/http-backend-handle-proto-header and kr/doc-webserver-config-for-v2.
The latter does give some specific nginx tips which I didn't carry over,
but they shouldn't be necessary after the change in http-backend. If we
do want to include them, they can be mentioned as optional if we later
add an nginx example config to the http-backend manpage.

  [1/5]: t5551: test v2-to-v0 http protocol fallback
  [2/5]: http-backend: handle HTTP_GIT_PROTOCOL CGI variable
  [3/5]: docs/http-backend: mention v2 protocol
  [4/5]: docs/git: discuss server-side config for GIT_PROTOCOL
  [5/5]: docs/protocol-v2: point readers transport config discussion

 Documentation/git-http-backend.txt      | 26 ++++++++++++++++++++++++-
 Documentation/git-upload-pack.txt       |  8 ++++++++
 Documentation/git.txt                   | 15 ++++++++++++++
 Documentation/technical/protocol-v2.txt |  8 +++++++-
 http-backend.c                          |  4 ++++
 t/lib-httpd/apache.conf                 |  7 +++++--
 t/t5551-http-fetch-smart.sh             |  9 +++++++++
 7 files changed, 73 insertions(+), 4 deletions(-)

-Peff

  reply	other threads:[~2021-09-10 14:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-04 15:17 [PATCH] Docs: web server must setenv GIT_PROTOCOL for v2 Konstantin Ryabitsev
2021-09-04 15:55 ` Jeff King
2021-09-07 20:57   ` Junio C Hamano
2021-09-07 21:11   ` Konstantin Ryabitsev
2021-09-08 10:48     ` Jeff King
2021-09-08 10:57       ` Jeff King
2021-09-08 16:50         ` Eric Wong
2021-09-09 17:28         ` Junio C Hamano
2021-09-09 17:35           ` Junio C Hamano
2021-09-10 11:39             ` Jeff King
2021-09-10 14:02               ` Jeff King [this message]
2021-09-10 14:04                 ` [PATCH 1/5] t5551: test v2-to-v0 http protocol fallback Jeff King
2021-09-10 14:05                 ` [PATCH 2/5] http-backend: handle HTTP_GIT_PROTOCOL CGI variable Jeff King
2021-09-10 14:09                 ` [PATCH 3/5] docs/http-backend: mention v2 protocol Jeff King
2021-09-10 14:09                 ` [PATCH 4/5] docs/git: discuss server-side config for GIT_PROTOCOL Jeff King
2021-09-10 14:10                 ` [PATCH 5/5] docs/protocol-v2: point readers transport config discussion Jeff King
2021-09-10 22:08                 ` [PATCH] Docs: web server must setenv GIT_PROTOCOL for v2 Junio C Hamano
2021-09-09 17:50         ` Philippe Blain
2021-09-10  5:39           ` Junio C Hamano
2021-09-10 11:40             ` Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YTtleYs48A1NpUpp@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=levraiphilippeblain@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.