All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <derrickstolee@github.com>
Cc: git@vger.kernel.org
Subject: Re: ds/* (was Re: What's cooking in git.git (Aug 2022, #06; Wed, 17))
Date: Thu, 18 Aug 2022 10:39:19 -0700	[thread overview]
Message-ID: <xmqqilmppi2g.fsf@gitster.g> (raw)
In-Reply-To: <fbcb87f4-00fa-3371-e108-a104be7ae501@github.com> (Derrick Stolee's message of "Thu, 18 Aug 2022 11:00:18 -0400")

Derrick Stolee <derrickstolee@github.com> writes:

> On 8/17/2022 10:23 PM, Junio C Hamano wrote:
>
>> * ds/bundle-uri-clone (2022-08-10) 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".
>>  source: <pull.1300.v3.git.1660050703.gitgitgadget@gmail.com>
>
> This series has been stable for a while. Please consider merging it
> to 'next' when you are ready.

I think earlier rounds of this series were fairly well reviewed and
the interdiff in the cover letter has nothing questionable.

>> * 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>
>
> This has been stable for a few What's Cooking mails. Should be
> ready to go.

This one I am not as confident as the other one, though.  I actually
was thinking that this may be getting stale, not stable, without any
further "I read it once again and this round looks good" X-<.  Let
me see if I can find time to read it over before I decide.

Thanks.




  reply	other threads:[~2022-08-18 17:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18  2:23 What's cooking in git.git (Aug 2022, #06; Wed, 17) Junio C Hamano
2022-08-18 12:42 ` js/bisect-in-c (was: What's cooking in git.git (Aug 2022, #06; Wed, 17)) Ævar Arnfjörð Bjarmason
2022-08-19 11:06   ` Johannes Schindelin
2022-08-19 14:28     ` Ævar Arnfjörð Bjarmason
2022-08-18 13:18 ` What's cooking in git.git (Aug 2022, #06; Wed, 17) Derrick Stolee
2022-08-18 13:19   ` Derrick Stolee
2022-08-18 15:00 ` ds/* (was Re: What's cooking in git.git (Aug 2022, #06; Wed, 17)) Derrick Stolee
2022-08-18 17:39   ` Junio C Hamano [this message]
2022-08-18 18:12 ` vd/* (was: " Victoria Dye
2022-08-18 19:09   ` vd/* Junio C Hamano
2022-08-18 22:42 ` What's cooking in git.git (Aug 2022, #06; Wed, 17) Jonathan Tan

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=xmqqilmppi2g.fsf@gitster.g \
    --to=gitster@pobox.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.