From: Glen Choo <chooglen@google.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2021, #05; Fri, 19)
Date: Mon, 22 Nov 2021 10:00:20 -0800 [thread overview]
Message-ID: <kl6lr1b8qde3.fsf@chooglen-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <xmqqa6hznvz1.fsf@gitster.g>
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?
next prev parent reply other threads:[~2021-11-22 18:00 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 ` Glen Choo [this message]
2021-11-22 18:05 ` What's cooking in git.git (Nov 2021, #05; Fri, 19) Junio C Hamano
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
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=kl6lr1b8qde3.fsf@chooglen-macbookpro.roam.corp.google.com \
--to=chooglen@google.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).