From: Brandon Williams <bmwill@google.com>
To: git@vger.kernel.org
Cc: Brandon Williams <bmwill@google.com>,
sbeller@google.com, jrnieder@gmail.com, gitster@pobox.com
Subject: [PATCH v2 0/2] push options across http
Date: Wed, 22 Mar 2017 15:21:58 -0700 [thread overview]
Message-ID: <20170322222200.103204-1-bmwill@google.com> (raw)
In-Reply-To: <20170322195102.165314-1-bmwill@google.com>
v2 addresses Jonathan's comments from v1.
* Fix a test
* Add some documentation
* remove short option from --push-option in git send-pack
Brandon Williams (2):
send-pack: send push options correctly in stateless-rpc case
remote-curl: allow push options
Documentation/git-send-pack.txt | 6 ++++++
builtin/send-pack.c | 5 +++++
remote-curl.c | 8 ++++++++
send-pack.c | 20 ++++++++------------
t/t5545-push-options.sh | 33 +++++++++++++++++++++++++++++++--
5 files changed, 58 insertions(+), 14 deletions(-)
--
2.12.1.500.gab5fba24ee-goog
next prev parent reply other threads:[~2017-03-22 22:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 19:51 [PATCH 0/2] push options across http Brandon Williams
2017-03-22 19:51 ` [PATCH 1/2] send-pack: send push options correctly in stateless-rpc case Brandon Williams
2017-03-22 21:15 ` Jonathan Nieder
2017-03-22 22:19 ` Brandon Williams
2017-03-22 19:51 ` [PATCH 2/2] remote-curl: allow push options Brandon Williams
2017-03-22 21:26 ` Junio C Hamano
2017-03-22 21:36 ` Brandon Williams
2017-03-22 21:38 ` Jonathan Nieder
2017-03-22 22:13 ` Brandon Williams
2017-03-22 21:17 ` [PATCH 0/2] push options across http Junio C Hamano
2017-03-22 21:20 ` Stefan Beller
2017-03-22 22:21 ` Brandon Williams [this message]
2017-03-22 22:21 ` [PATCH v2 1/2] send-pack: send push options correctly in stateless-rpc case Brandon Williams
2017-03-22 22:22 ` [PATCH v2 2/2] remote-curl: allow push options Brandon Williams
2017-03-22 22:29 ` [PATCH v2 0/2] push options across http Jonathan Nieder
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=20170322222200.103204-1-bmwill@google.com \
--to=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=sbeller@google.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 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 NNTP newsgroup(s).