From: Derrick Stolee <derrickstolee@github.com>
To: "Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: What's cooking in git.git (Jun 2022, #01; Wed, 1)
Date: Thu, 2 Jun 2022 08:25:22 -0400 [thread overview]
Message-ID: <383beb65-d507-18f2-24e4-f4bf23e7d99e@github.com> (raw)
In-Reply-To: <xmqqee07q3xc.fsf@gitster.g>
On 6/1/2022 8:55 PM, Junio C Hamano wrote:
> * ds/bundle-uri-more (2022-05-20) 24 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
> (this branch uses ds/bundle-uri.)
>
> RFC/ seems to trigger errors in linux-leaks CI job
> source: <pull.1234.git.1653072042.gitgitgadget@gmail.com>
I'm not surprised about failing the linux-leaks job, but I'm
sorry that it is causing noise. Please eject from 'seen' to
reduce the noise here.
I also haven't had any feedback on this RFC series, so I plan
to break out the first few patches and clean them up for full
submission soon. I've seen more feedback on topics that might
be candidates for merging.
Thanks,
-Stolee
next prev parent reply other threads:[~2022-06-02 12:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 0:55 What's cooking in git.git (Jun 2022, #01; Wed, 1) Junio C Hamano
2022-06-02 1:16 ` gc/zero-length-branch-config-fix (was Re: What's cooking in git.git (Jun 2022, #01; Wed, 1)) Glen Choo
2022-06-02 8:37 ` Ævar Arnfjörð Bjarmason
2022-06-02 12:13 ` ab/env-array (was: " Ævar Arnfjörð Bjarmason
2022-06-02 12:25 ` Derrick Stolee [this message]
2022-06-02 14:07 ` What's cooking in git.git (Jun 2022, #01; Wed, 1) Jeff Hostetler
2022-06-02 14:46 ` ab/bug-if-bug (was: What's cooking in git.git (Jun 2022, #01; Wed, 1)) Ævar Arnfjörð Bjarmason
2022-06-02 14:47 ` ab/hooks-regression-fix " Ævar Arnfjörð Bjarmason
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=383beb65-d507-18f2-24e4-f4bf23e7d99e@github.com \
--to=derrickstolee@github.com \
--cc=avarab@gmail.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 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 NNTP newsgroup(s).