From: Derrick Stolee <derrickstolee@github.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: ds/* (was What's cooking in git.git (Aug 2022, #03; Mon, 8))
Date: Tue, 9 Aug 2022 09:16:44 -0400 [thread overview]
Message-ID: <d8a20d85-ab00-cb03-765b-e1d080de422b@github.com> (raw)
In-Reply-To: <xmqqv8r2qoi4.fsf@gitster.g>
On 8/8/2022 7:55 PM, Junio C Hamano wrote:
> * ds/bundle-uri-clone (2022-08-02) 5 commits
> - clone: --bundle-uri cannot be combined with --depth
> - bundle-uri: add support for http(s):// and file://
> - clone: add --bundle-uri option
> - bundle-uri: create basic file-copy logic
> - remote-curl: add 'get' capability
>
> Implement "git clone --bundle-uri".
>
> Expecting a reroll.
> cf. <9afd5eb2-44a0-6342-6006-5dbdefba9947@github.com>
> source: <pull.1300.v2.git.1659443384.gitgitgadget@gmail.com>
I just sent v3 [1], including the updates to the protocol parsing.
[1] https://lore.kernel.org/git/pull.1300.v3.git.1660050703.gitgitgadget@gmail.com
> * ds/bundle-uri-more (2022-07-25) 2 commits
> - bundle-uri: add example bundle organization
> - docs: document bundle URI standard
>
> The "bundle URI" topic.
>
> Needs review.
> source: <pull.1248.v3.git.1658757188.gitgitgadget@gmail.com>
I just sent v4 [2], including minor rewords of things. Now that this was
reviewed by Josh, Matthew, and yourself, do you still feel that more
review is required?
[2] https://lore.kernel.org/git/pull.1248.v4.git.1660050761.gitgitgadget@gmail.com
> * ds/decorate-filter-tweak (2022-08-05) 11 commits
> - fetch: use ref_namespaces during prefetch
> - maintenance: stop writing log.excludeDecoration
> - log: create log.initialDecorationSet=all
> - log: add --clear-decorations option
> - log: add default decoration filter
> - log-tree: use ref_namespaces instead of if/else-if
> - refs: use ref_namespaces for replace refs base
> - refs: add array of ref namespaces
> - t4207: test coloring of grafted decorations
> - t4207: modernize test
> - refs: allow "HEAD" as decoration filter
>
> The namespaces used by "log --decorate" from "refs/" hierarchy by
> default has been tightened.
>
> Will merge to 'next'?
> source: <pull.1301.v3.git.1659722323.gitgitgadget@gmail.com>
I think review has stabilized on this series.
Thanks,
-Stolee
next prev parent reply other threads:[~2022-08-09 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 23:55 What's cooking in git.git (Aug 2022, #03; Mon, 8) Junio C Hamano
2022-08-09 13:16 ` Derrick Stolee [this message]
2022-08-09 16:49 ` ds/* (was What's cooking in git.git (Aug 2022, #03; Mon, 8)) 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d8a20d85-ab00-cb03-765b-e1d080de422b@github.com \
--to=derrickstolee@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.
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).