From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Glen Choo <chooglen@google.com>, git@vger.kernel.org
Subject: Re: gc/bare-repo-discovery (was Re: What's cooking in git.git (Jul 2022, #03; Mon, 11))
Date: Thu, 14 Jul 2022 11:27:19 -0700 [thread overview]
Message-ID: <xmqqmtdb5z3s.fsf@gitster.g> (raw)
In-Reply-To: <5ps2q552-1rr3-7161-4181-31556pp2ns12@tzk.qr> (Johannes Schindelin's message of "Thu, 14 Jul 2022 18:17:39 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> I would find `safe.bareRepository = true` or `false` more intuitive, and
> more concise.
Yup, that is fine by me.
> And if there should be an option to ignore bare repositories when
> discovering a Git repository, it could be a tristate, with `ignore` being
> the value to trigger that mode.
Sounds good.
next prev parent reply other threads:[~2022-07-14 18:27 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 ` gc/bare-repo-discovery (was Re: What's cooking in git.git (Jul 2022, #03; Mon, 11)) Glen Choo
2022-07-13 16:29 ` Junio C Hamano
2022-07-14 16:17 ` Johannes Schindelin
2022-07-14 18:27 ` Junio C Hamano [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqmtdb5z3s.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=chooglen@google.com \
--cc=git@vger.kernel.org \
/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.