From: Brandon Williams <bmwill@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] remote-curl: allow push options
Date: Wed, 22 Mar 2017 14:36:34 -0700 [thread overview]
Message-ID: <20170322213634.GB11254@google.com> (raw)
In-Reply-To: <xmqqo9wthukz.fsf@gitster.mtv.corp.google.com>
On 03/22, Junio C Hamano wrote:
> Brandon Williams <bmwill@google.com> writes:
>
> > Teach remote-curl to understand push options and to be able to convey
> > them across HTTP.
> >
> > Signed-off-by: Brandon Williams <bmwill@google.com>
> > ---
>
> An earlier 438fc684 ("push options: pass push options to the
> transport helper", 2017-02-08) said:
>
> ...
> Fix this by propagating the push options to the transport helper.
>
> This is only addressing the first issue of
> (1) the helper protocol does not propagate push-option
> (2) the http helper is not prepared to handle push-option
>
> Once we fix (2), the http transport helper can make use of push options
> as well, but that happens as a follow up. (1) is a bug fix, whereas (2)
> is a feature, which is why we only do (1) here.
>
> and this is the step (2) to complete what it started?
Yep! As far as I understand from looking at that commit, push options
were being passed to remote-curl and remote-curl was silently ignoring
them. So that patch made it complain when a remote-helper didn't
support push options.
This patch teaches remote-curl to actually support push options, fixing
(2).
--
Brandon Williams
next prev parent reply other threads:[~2017-03-22 21:36 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 [this message]
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 ` [PATCH v2 " Brandon Williams
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=20170322213634.GB11254@google.com \
--to=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).