From: Taylor Blau <me@ttaylorr.com>
To: Glen Choo <chooglen@google.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Derrick Stolee <derrickstolee@github.com>
Subject: Re: gc/bare-repo-discovery (was Re: What's cooking in git.git (Jun 2022, #04; Mon, 13))
Date: Thu, 16 Jun 2022 17:58:10 -0400 [thread overview]
Message-ID: <YquncgVEpWIG7lJ7@nand.local> (raw)
In-Reply-To: <kl6lzgid4u5p.fsf@chooglen-macbookpro.roam.corp.google.com>
On Wed, Jun 15, 2022 at 12:13:22PM -0700, Glen Choo wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>
> > * gc/bare-repo-discovery (2022-06-07) 5 commits
> > - setup.c: create `discovery.bare`
> > - safe.directory: use git_protected_config()
> > - config: read protected config with `git_protected_config()`
> > - Documentation: define protected configuration
> > - Documentation/git-config.txt: add SCOPES section
> >
> > Introduce a discovery.barerepository configuration variable that
> > allows users to forbid discovery of bare repositories.
> >
> > Expecting a reroll.
> > source: <29053d029f8ec61095a2ad557be38b1d485a158f.1654635432.git.gitgitgadget@gmail.com>
>
> v4 hasn't been reviewed yet. I think "Needs Review" is more accurate.
Yep, I agree that we can move this to "needs review". FWIW, I've been
meaning to look at the more recent iterations of this series, but
haven't quite gotten to it yet.
Thanks,
Taylor
next prev parent reply other threads:[~2022-06-16 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 1:46 What's cooking in git.git (Jun 2022, #04; Mon, 13) Junio C Hamano
2022-06-15 19:13 ` gc/bare-repo-discovery (was Re: What's cooking in git.git (Jun 2022, #04; Mon, 13)) Glen Choo
2022-06-16 21:58 ` Taylor Blau [this message]
2022-06-15 19:17 ` gc/submodule-update " Glen Choo
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=YquncgVEpWIG7lJ7@nand.local \
--to=me@ttaylorr.com \
--cc=chooglen@google.com \
--cc=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).