From: Brandon Williams <bmwill@google.com>
To: git@vger.kernel.org, bmwill@google.com
Cc: Brandon Williams <bmwill@google.com>
Subject: [PATCH 0/3] optionally send server-options when using v2
Date: Mon, 23 Apr 2018 15:46:21 -0700 [thread overview]
Message-ID: <20180423224624.213341-1-bmwill@google.com> (raw)
Building on top of protocol version 2 this series adds the ability to
optionally send server specific options when using protocol v2. This
resembles the "push-options" feature except server options are sent as
capability lines during a command request allowing for all current and
future commands to benefit from sending arbitrary server options (and
not requiring that sending server specific options be re-implemented for
each and every command that may want to make use of them in the future).
These options can be provided by the user via the command line by giving
"-o <option>" or "--server-option=<option>" to either ls-remote or
fetch.
Command request example:
command=fetch
server-option=hello
server-option=world
0001
want A
want B
have X
have Y
0000
These options are only transmitted to the remote end when communicating
using protocol version 2.
Brandon Williams (3):
serve: introduce the server-option capability
ls-remote: send server options when using protocol v2
fetch: send server options when using protocol v2
Documentation/fetch-options.txt | 8 +++++++
Documentation/git-ls-remote.txt | 8 +++++++
Documentation/technical/protocol-v2.txt | 10 ++++++++
builtin/fetch.c | 5 ++++
builtin/ls-remote.c | 4 ++++
connect.c | 9 ++++++-
fetch-pack.c | 7 ++++++
fetch-pack.h | 1 +
remote.h | 4 +++-
serve.c | 1 +
t/t5701-git-serve.sh | 21 ++++++++++++++++
t/t5702-protocol-v2.sh | 32 +++++++++++++++++++++++++
transport.c | 3 ++-
transport.h | 6 +++++
14 files changed, 116 insertions(+), 3 deletions(-)
--
2.17.0.484.g0c8726318c-goog
next reply other threads:[~2018-04-23 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 22:46 Brandon Williams [this message]
2018-04-23 22:46 ` [PATCH 1/3] serve: introduce the server-option capability Brandon Williams
2018-04-23 22:46 ` [PATCH 2/3] ls-remote: send server options when using protocol v2 Brandon Williams
2018-04-23 22:46 ` [PATCH 3/3] fetch: " Brandon Williams
2018-04-23 22:47 ` [PATCH 0/3] optionally send server-options when using v2 Brandon Williams
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180423224624.213341-1-bmwill@google.com \
--to=bmwill@google.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).