From: Brandon Williams <bmwill@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2018, #04; Mon, 30)
Date: Wed, 2 May 2018 16:17:16 -0700 [thread overview]
Message-ID: <20180502231716.GB122314@google.com> (raw)
In-Reply-To: <xmqq4ljtz87g.fsf@gitster-ct.c.googlers.com>
On 04/30, Junio C Hamano wrote:
> * bw/protocol-v2 (2018-03-15) 35 commits
> (merged to 'next' on 2018-04-11 at 23ee234a2c)
> + remote-curl: don't request v2 when pushing
> + remote-curl: implement stateless-connect command
> + http: eliminate "# service" line when using protocol v2
> + http: don't always add Git-Protocol header
> + http: allow providing extra headers for http requests
> + remote-curl: store the protocol version the server responded with
> + remote-curl: create copy of the service name
> + pkt-line: add packet_buf_write_len function
> + transport-helper: introduce stateless-connect
> + transport-helper: refactor process_connect_service
> + transport-helper: remove name parameter
> + connect: don't request v2 when pushing
> + connect: refactor git_connect to only get the protocol version once
> + fetch-pack: support shallow requests
> + fetch-pack: perform a fetch using v2
> + upload-pack: introduce fetch server command
> + push: pass ref prefixes when pushing
> + fetch: pass ref prefixes when fetching
> + ls-remote: pass ref prefixes when requesting a remote's refs
> + transport: convert transport_get_remote_refs to take a list of ref prefixes
> + transport: convert get_refs_list to take a list of ref prefixes
> + connect: request remote refs using v2
> + ls-refs: introduce ls-refs server command
> + serve: introduce git-serve
> + test-pkt-line: introduce a packet-line test helper
> + protocol: introduce enum protocol_version value protocol_v2
> + transport: store protocol version
> + connect: discover protocol version outside of get_remote_heads
> + connect: convert get_remote_heads to use struct packet_reader
> + transport: use get_refs_via_connect to get refs
> + upload-pack: factor out processing lines
> + upload-pack: convert to a builtin
> + pkt-line: add delim packet support
> + pkt-line: allow peeking a packet line without consuming it
> + pkt-line: introduce packet_read_with_status
> (this branch is used by bw/server-options.)
>
> The beginning of the next-gen transfer protocol.
>
> Will merge to 'master'.
Awesome, I see you're already planning on merging this! I was just
going to drop by and saw that internal testing showed that this *should*
be ready to be merged to master :) Thanks!
--
Brandon Williams
next prev parent reply other threads:[~2018-05-02 23:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 3:25 What's cooking in git.git (Apr 2018, #04; Mon, 30) Junio C Hamano
2018-04-30 15:33 ` SZEDER Gábor
2018-05-01 13:46 ` Johannes Schindelin
2018-05-02 3:59 ` Junio C Hamano
2018-05-02 6:53 ` Johannes Schindelin
2018-05-02 10:46 ` Junio C Hamano
2018-05-02 1:36 ` Junio C Hamano
2018-04-30 19:17 ` js/no-pager-shorthand [was: What's cooking in git.git (Apr 2018, #04; Mon, 30)] Johannes Sixt
2018-05-01 11:57 ` Johannes Schindelin
2018-05-01 14:58 ` Johannes Sixt
2018-05-01 18:10 ` Eric Sunshine
2018-05-02 1:43 ` js/no-pager-shorthand [ Junio C Hamano
2018-05-01 18:46 ` js/no-pager-shorthand [was: What's cooking in git.git (Apr 2018, #04; Mon, 30)] Ævar Arnfjörð Bjarmason
2018-05-02 23:17 ` Brandon Williams [this message]
2018-05-04 18:04 ` What's cooking in git.git (Apr 2018, #04; Mon, 30) Elijah Newren
2018-05-07 4:39 ` 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=20180502231716.GB122314@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 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.