git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Glen Choo <chooglen@google.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Taylor Blau <me@ttaylorr.com>
Subject: gc/bare-repo-discovery (was Re: What's cooking in git.git (Jul 2022, #01; Fri, 1))
Date: Wed, 06 Jul 2022 10:56:36 -0700	[thread overview]
Message-ID: <kl6lh73urup7.fsf@chooglen-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <xmqqo7y85t44.fsf@gitster.g>

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?)

  parent reply	other threads:[~2022-07-06 17:56 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 ` Glen Choo [this message]
2022-07-06 22:15   ` gc/bare-repo-discovery (was " Junio C Hamano

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=kl6lh73urup7.fsf@chooglen-macbookpro.roam.corp.google.com \
    --to=chooglen@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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. 
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).