From: Junio C Hamano <gitster@pobox.com>
To: Glen Choo <chooglen@google.com>
Cc: git@vger.kernel.org, Taylor Blau <me@ttaylorr.com>
Subject: Re: gc/bare-repo-discovery (was Re: What's cooking in git.git (Jul 2022, #01; Fri, 1))
Date: Wed, 06 Jul 2022 15:15:55 -0700 [thread overview]
Message-ID: <xmqq1quxhopw.fsf@gitster.g> (raw)
In-Reply-To: <kl6lh73urup7.fsf@chooglen-macbookpro.roam.corp.google.com> (Glen Choo's message of "Wed, 06 Jul 2022 10:56:36 -0700")
Glen Choo <chooglen@google.com> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> * gc/bare-repo-discovery (2022-06-30) 5 commits
>> - setup.c: create `discovery.bare`
>> - safe.directory: use git_protected_config()
>> - config: learn `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.
>>
>> Will merge to 'next'?
>> source: <pull.1261.v6.git.git.1656612839.gitgitgadget@gmail.com>
>
> I'll send a reroll soon. Taylor Blau left a bunch of great
> comments/suggestions that I intend to address (though I don't think any
> of them were meant to be blocking?)
OK. I too found Taylor's comments very helpful.
Thanks for a status update.
prev parent reply other threads:[~2022-07-06 22:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 23:08 What's cooking in git.git (Jul 2022, #01; Fri, 1) Junio C Hamano
2022-07-04 8:12 ` gc/submodule-use-super-prefix & ab/submodule-cleanup (was: What's cooking in git.git (Jul 2022, #01; Fri, 1)) Ævar Arnfjörð Bjarmason
2022-07-06 16:57 ` Glen Choo
2022-07-04 13:15 ` ds/rebase-update-re (was " Derrick Stolee
2022-07-04 15:59 ` Junio C Hamano
2022-07-04 16:58 ` Elijah Newren
2022-07-04 20:17 ` Derrick Stolee
2022-07-05 1:31 ` en/merge-dual-dir-renames-fix (Was: " Elijah Newren
2022-07-06 17:56 ` gc/bare-repo-discovery (was " Glen Choo
2022-07-06 22:15 ` Junio C Hamano [this message]
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=xmqq1quxhopw.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=chooglen@google.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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 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.