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

Re: What's cooking in git.git (Oct 2018, #02; Sat, 13)

From
Josh Steadmon <steadmon@google.com>
Date
Oct 16, 2018, 21:20 UTC
Message-ID
<20181016212008.GA249669@google.com>
In-Reply-To
<xmqqh8hr9pxb.fsf@gitster-ct.c.googlers.com>
On 2018.10.12 23:53, Junio C Hamano wrote:
Show 13 quoted lines
> * 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
Previous: Stefan BellerNext: Junio C Hamano
Message 7 of 8 in “What's cooking in git.git (Oct 2018, #02; Sat, 13)”
  1. Junio C HamanoOct 12, 2018
  2. Ævar Arnfjörð BjarmasonOct 12, 2018
  3. Stefan BellerOct 12, 2018
  4. Stefan BellerOct 12, 2018
  5. Junio C HamanoOct 13, 2018
  6. Stefan BellerOct 15, 2018
  7. Josh SteadmonOct 16, 2018
  8. Junio C HamanoOct 16, 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.