git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <derrickstolee@github.com>
Cc: git@vger.kernel.org, avarab@gmail.com
Subject: Re: ds/bundle-uri (was Re: What's cooking in git.git (May 2022, #06; Fri, 20))
Date: Mon, 23 May 2022 13:09:42 -0700	[thread overview]
Message-ID: <xmqqh75gqad5.fsf@gitster.g> (raw)
In-Reply-To: <a467d972-85a6-f4b0-7ec7-184add308e25@github.com> (Derrick Stolee's message of "Sat, 21 May 2022 14:07:14 -0400")

Derrick Stolee <derrickstolee@github.com> writes:

> On 5/21/22 3:55 AM, Junio C Hamano wrote:
>
>> * ds/bundle-uri (2022-05-20) 32 commits
>>  - t5601: basic bundle URI tests
>>  - clone: unbundle the advertised bundles
>>  - bundle-uri: download bundles from an advertised list
>>  - bundle-uri: allow relative URLs in bundle lists
>>  - bundle-uri client: add boolean transfer.bundleURI setting
>>  - bundle-uri: serve URI advertisement from bundle.* config
>>  - bundle-uri client: add "git ls-remote-bundle-uri"
>>  - bundle-uri client: add minimal NOOP client
>>  - protocol v2: add server-side "bundle-uri" skeleton
>>  - bundle-uri: fetch a list of bundles
>>  - bundle-uri: parse bundle list in config format
>>  - bundle-uri: limit recursion depth for bundle lists
>>  - bundle-uri: unit test "key=value" parsing
>>  - bundle-uri: create "key=value" line parsing
>>  - bundle-uri: create base key-value pair parsing
>>  - bundle-uri: create bundle_list struct and helpers
>>  - clone: --bundle-uri cannot be combined with --depth
>>  - clone: add --bundle-uri option
>>  - fetch: add 'refs/bundle/' to log.excludeDecoration
>>  - fetch: add --bundle-uri option
>>  - bundle-uri: add support for http(s):// and file://
>>  - bundle-uri: create basic file-copy logic
>>  - remote-curl: add 'get' capability
>>  - docs: document bundle URI standard
> ...
>>  source: <pull.1234.git.1653072042.gitgitgadget@gmail.com>
>
> These patches are for the combined bundle URI RFC. I
> appreciate that you're tracking them, but they aren't ready
> for full review, since they are missing a lot of tests.
> First, we need to establish that the overall design is a
> good approach. After that consensus is reached, I expect
> that this series to be split into several parts that are
> more manageable to review bit-by-bit. 

Split the above into a separate topic; thanks.

  reply	other threads:[~2022-05-23 20:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-21  7:55 What's cooking in git.git (May 2022, #06; Fri, 20) Junio C Hamano
2022-05-21 18:07 ` ds/bundle-uri (was Re: What's cooking in git.git (May 2022, #06; Fri, 20)) Derrick Stolee
2022-05-23 20:09   ` Junio C Hamano [this message]
2022-05-21 22:02 ` js/use-builtin-add-i, was Re: What's cooking in git.git (May 2022, #06; Fri, 20) Johannes Schindelin
2022-05-23 17:41   ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqh75gqad5.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=derrickstolee@github.com \
    --cc=git@vger.kernel.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).