From: Junio C Hamano <gitster@pobox•com>
To: Glen Choo <chooglen@google•com>
Cc: git@vger•kernel.org
Subject: Re: What's cooking in git.git (Nov 2021, #05; Fri, 19)
Date: Mon, 22 Nov 2021 10:05:12 -0800 [thread overview]
Message-ID: <xmqqbl2cgj6v.fsf@gitster.g> (raw)
In-Reply-To: <kl6lr1b8qde3.fsf@chooglen-macbookpro.roam.corp.google.com> (Glen Choo's message of "Mon, 22 Nov 2021 10:00:20 -0800")
Glen Choo <chooglen@google•com> writes:
> Junio C Hamano <gitster@pobox•com> writes:
>
>> * gc/remote-with-fewer-static-global-variables (2021-11-18) 5 commits
>> - remote: die if branch is not found in repository
>> - remote: remove the_repository->remote_state from static methods
>> - remote: use remote_state parameter internally
>> - remote: move static variables into per-repository struct
>> - t5516: add test case for pushing remote refspecs
>>
>> Code clean-up to eventually allow information on remotes defined
>> for an arbitrary repository to be read.
>>
>> Will merge to 'next'?
>
> This got a Reviewed-by from Jonathan Tan; do we need more reviewers to
> look at this?
As I promised, I've been ignoring anything that won't be in 2.34.1
until it goes out, so I do not know the answer to that question at
this moment ;-)
next prev parent reply other threads:[~2021-11-22 18:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-20 7:10 What's cooking in git.git (Nov 2021, #05; Fri, 19) Junio C Hamano
2021-11-20 11:18 ` Fabian Stelzer
2021-11-20 17:30 ` Elijah Newren
2021-11-20 22:20 ` vd/sparse-reset (Was: Re: What's cooking in git.git (Nov 2021, #05; Fri, 19)) Elijah Newren
2021-11-21 2:00 ` What's cooking in git.git (Nov 2021, #05; Fri, 19) Elijah Newren
2021-11-22 17:59 ` vd/sparse-sparsity-fix-on-read (Was: Re: What's cooking in git.git (Nov 2021, #05; Fri, 19)) Elijah Newren
2021-11-22 18:00 ` What's cooking in git.git (Nov 2021, #05; Fri, 19) Glen Choo
2021-11-22 18:05 ` Junio C Hamano [this message]
2021-11-22 22:36 ` Glen Choo
2021-11-23 13:22 ` ab/mark-leak-free-tests-even-more (was: What's cooking in git.git (Nov 2021, #05; Fri, 19)) Æ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=xmqqbl2cgj6v.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=chooglen@google$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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