gc/bare-repo-discovery (was Re: What's cooking in git.git (Jul 2022, #03; Mon, 11))

From: Glen Choo <chooglen@google.com>
Date: Jul 12, 2022, 22:19 UTC
Message-ID: <kl6lpmia55ys.fsf@chooglen-macbookpro.roam.corp.google.com>
In-Reply-To: <xmqqo7xufee7.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

> Maintenance releases v2.37.1 and others have been tagged.  They are
> to address CVE-2022-29187, a vulnerability related to CVE-2022-24765
> that was fixed earlier.  Big thanks to Carlo Arenas and Johannes
> Schindelin for fixing the issue and helping the releases out.

\o/ thanks everyone!

Show 12 quoted lines

> * gc/bare-repo-discovery (2022-07-07) 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.v7.git.git.1657234914.gitgitgadget@gmail.com>

I have a (hopefully final) reroll planned that takes your documentation suggestions. I think it reads a lot better with those, so thanks!

I also noted your distaste for the `discovery.*` namespace (fair enough). To avoid a reroll-of-the-reroll, I was hoping that we could agree on something on-list (thread here [1]) before I send out the next version.

[1] https://lore.kernel.org/git/kl6lsfn656cw.fsf@chooglen-macbookpro.roam.corp.google.com