From: Victoria Dye <vdye@github.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: ds/bundle-uri-5 (was: Re: What's cooking in git.git (Feb 2023, #01; Thu, 2))
Date: Wed, 8 Feb 2023 09:22:53 -0800 [thread overview]
Message-ID: <4f48047d-50c2-5f59-82e0-dbafd3b380d3@github.com> (raw)
In-Reply-To: <xmqqr0v7o0pp.fsf@gitster.g>
Junio C Hamano wrote:
> * ds/bundle-uri-5 (2023-01-31) 11 commits
> - bundle-uri: test missing bundles with heuristic
> - bundle-uri: store fetch.bundleCreationToken
> - fetch: fetch from an external bundle URI
> - bundle-uri: drop bundle.flag from design doc
> - clone: set fetch.bundleURI if appropriate
> - bundle-uri: download in creationToken order
> - bundle-uri: parse bundle.<id>.creationToken values
> - bundle-uri: parse bundle.heuristic=creationToken
> - t5558: add tests for creationToken heuristic
> - bundle: verify using check_connected()
> - bundle: test unbundling with incomplete history
>
> The bundle-URI subsystem adds support for creation-token heuristics
> to help incremental fetches.
>
> Will merge to 'next'?
> source: <pull.1454.v3.git.1675171759.gitgitgadget@gmail.com>
Apologies for not responding sooner, but I reviewed the most recent version
of this series and all of my previous feedback was addressed. Overall, I
think it looks good and is ready for merging to 'next'.
Thanks!
-Victoria
prev parent reply other threads:[~2023-02-08 17:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 4:02 What's cooking in git.git (Feb 2023, #01; Thu, 2) Junio C Hamano
2023-02-04 9:33 ` Sergey Organov
2023-02-06 18:35 ` Junio C Hamano
2023-02-06 21:35 ` Sergey Organov
2023-03-01 18:40 ` Sergey Organov
2023-03-01 22:15 ` Junio C Hamano
2023-03-01 22:26 ` Sergey Organov
2023-03-01 23:54 ` Glen Choo
2023-03-02 14:38 ` Sergey Organov
2023-02-07 4:06 ` so/diff-merges-more (was Re: What's cooking in git.git (Feb 2023, #01; Thu, 2)) Glen Choo
2023-02-07 12:50 ` Sergey Organov
2023-03-02 0:37 ` Glen Choo
2023-03-02 16:15 ` Junio C Hamano
2023-03-02 16:57 ` Sergey Organov
2023-03-06 22:22 ` Glen Choo
2023-03-07 10:02 ` Sergey Organov
2023-03-07 17:54 ` Junio C Hamano
2023-03-08 22:19 ` Sergey Organov
2023-03-08 23:08 ` Junio C Hamano
2023-03-09 13:54 ` Sergey Organov
2023-03-09 17:43 ` Glen Choo
2023-03-09 19:56 ` Sergey Organov
2023-03-10 21:19 ` Glen Choo
2023-03-10 21:47 ` Junio C Hamano
2023-03-17 14:18 ` Sergey Organov
2023-03-18 0:08 ` Junio C Hamano
2023-03-25 16:55 ` Sergey Organov
2023-03-29 7:43 ` Sergey Organov
2023-03-29 8:06 ` Sergey Organov
2023-02-08 17:22 ` Victoria Dye [this message]
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=4f48047d-50c2-5f59-82e0-dbafd3b380d3@github.com \
--to=vdye@github.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.
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).