git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Apr 2018, #03; Wed, 25)

From
Derrick Stolee <stolee@gmail.com>
Date
Apr 26, 2018, 12:44 UTC
Message-ID
<4d0bd1a2-2f51-4a11-7e31-1e1ac5213c51@gmail.com>
In-Reply-To
<20180425174300.GA49485@google.com>
On 4/25/2018 1:43 PM, Brandon Williams wrote:
Show 60 quoted lines
> On 04/25, Ævar Arnfjörð Bjarmason 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 cook in 'next'.
>> With a month & 10 days of no updates & this looking stable it would be
>> great to have it in master sooner than later to build on top of it in
>> the 2.18 window.
> I personally think that this series is ready to graduate to master but I
> mentioned to Junio off-list that it might be a good idea to wait until
> it has undergone a little more stress testing.  We've been in the
> process of trying to get this rolled out to our internal server but due
> to a few roadblocks and people being out of the office its taken a bit
> longer than I would have liked to get it up and running.  I'm hoping in
> another few days/a week I'll have some more data on live traffic.  At
> that point I think I'll be more convinced that it will be safe to merge it.
>
> I may be overly cautions but I'm hoping that we can get this right
> without needing to do another protocol version bump for a very long
> time.  Technically using v2 is hidden behind an "experimental" config
> flag so we should still be able to tweak it after the fact if we
> absolutely needed to, but I'd like to avoid that if necessary.

There's no testing better than production. I think if we have an opportunity to test with realistic traffic, we should take advantage.

But I also agree that this series looks stable.

I realize it's hard to communicate both "this series is ready to merge" and "I appreciate your caution."

Thanks,
-Stolee
Previous: Brandon WilliamsNext: Johannes Schindelin
Message 4 of 12 in “What's cooking in git.git (Apr 2018, #03; Wed, 25)”
  1. Junio C HamanoApr 25, 2018
  2. Ævar Arnfjörð BjarmasonApr 25, 2018
  3. Brandon WilliamsApr 25, 2018
  4. Derrick StoleeApr 26, 2018
  5. Johannes SchindelinApr 27, 2018
  6. js/rebase-recreate-merge, was Re: What's cooking in git.git (Apr 2018, #03; Wed, 25)Johannes Schindelin, Apr 25, 2018
  7. Elijah NewrenApr 25, 2018
  8. Junio C HamanoApr 26, 2018
  9. brian m. carlsonApr 26, 2018
  10. Duy NguyenApr 26, 2018
  11. Eric SunshineApr 27, 2018
  12. Junio C HamanoApr 30, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.