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
Subject: gc/bare-repo-discovery (was Re: What's cooking in git.git (Jul 2022, #03; Mon, 11))
Date: Tue, 12 Jul 2022 15:19:55 -0700	[thread overview]
Message-ID: <kl6lpmia55ys.fsf@chooglen-macbookpro.roam.corp.google.com> (raw)
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!

> * 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

  reply	other threads:[~2022-07-12 22:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 17:07 What's cooking in git.git (Jul 2022, #03; Mon, 11) Junio C Hamano
2022-07-12 22:19 ` Glen Choo [this message]
2022-07-13 16:29   ` gc/bare-repo-discovery (was Re: What's cooking in git.git (Jul 2022, #03; Mon, 11)) Junio C Hamano
2022-07-14 16:17     ` Johannes Schindelin
2022-07-14 18:27       ` Junio C Hamano
2022-07-12 22:29 ` What's cooking in git.git (Jul 2022, #03; Mon, 11) Philip Oakley
2022-07-13 16:31   ` Junio C Hamano
2022-07-12 23:28 ` ac/bitmap-lookup-table (was: Re: What's cooking in git.git (Jul 2022, #03; Mon, 11)) Taylor Blau
2022-07-13 16:42   ` ac/bitmap-lookup-table Junio C Hamano
2022-07-13 11:10 ` js/bisect-in-c, was Re: What's cooking in git.git (Jul 2022, #03; Mon, 11) Johannes Schindelin
2022-07-13 11:18   ` Ævar Arnfjörð Bjarmason
2022-07-13 16:01     ` Junio C Hamano
2022-07-14  0:22       ` Ævar Arnfjörð Bjarmason
2022-07-14 19:35       ` Johannes Schindelin
2022-07-14 21:09         ` Ævar Arnfjörð Bjarmason
2022-08-16  8:51           ` Johannes Schindelin
2022-08-17  0:49             ` Æ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=kl6lpmia55ys.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).