From: Josh Steadmon <steadmon@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2018, #02; Sat, 13)
Date: Tue, 16 Oct 2018 14:20:08 -0700 [thread overview]
Message-ID: <20181016212008.GA249669@google.com> (raw)
In-Reply-To: <xmqqh8hr9pxb.fsf@gitster-ct.c.googlers.com>
On 2018.10.12 23:53, Junio C Hamano wrote:
> * js/remote-archive-v2 (2018-09-28) 4 commits
> (merged to 'next' on 2018-10-12 at 5f34377f60)
> + archive: allow archive over HTTP(S) with proto v2
> + archive: implement protocol v2 archive command
> + archive: use packet_reader for communications
> + archive: follow test standards around assertions
>
> The original implementation of "git archive --remote" more or less
> bypassed the transport layer and did not work over http(s). The
> version 2 of the protocol is defined to allow going over http(s) as
> well as Git native transport.
>
> Will merge to 'master'.
The first two patches (test cleanup and packet_reader refactor) are OK,
but the latter two will break the archive command when an old client
attempts to talk to a new server (due to the version advertisement
problem noted in [1]). Sorry that I didn't catch that these had made it
into next.
[1]: https://public-inbox.org/git/20180927223314.GA230445@google.com/#t
next prev parent reply other threads:[~2018-10-16 21:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 14:53 What's cooking in git.git (Oct 2018, #02; Sat, 13) Junio C Hamano
2018-10-12 15:02 ` Ævar Arnfjörð Bjarmason
2018-10-12 19:44 ` Stefan Beller
2018-10-12 23:37 ` Stefan Beller
2018-10-13 1:03 ` Junio C Hamano
2018-10-15 17:32 ` Stefan Beller
2018-10-16 21:20 ` Josh Steadmon [this message]
2018-10-16 23:11 ` Junio C Hamano
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=20181016212008.GA249669@google.com \
--to=steadmon@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 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.