From: Taylor Blau <me@ttaylorr.com>
To: Alex Henrie <alexhenrie24@gmail.com>
Cc: git@vger.kernel.org, Jens.Lehmann@web.de, gitster@pobox.com
Subject: Re: [PATCH] submodule: deprecate --recurse-submodules=""
Date: Wed, 23 Aug 2023 15:57:02 -0400 [thread overview]
Message-ID: <ZOZkjoknPJkhgNYf@nand.local> (raw)
In-Reply-To: <CAMMLpeRam03bmO0jnsbKQB7174xv12HJzTtC-6dHFbQDMKB5gA@mail.gmail.com>
On Wed, Aug 23, 2023 at 01:53:22PM -0600, Alex Henrie wrote:
> On the other hand, given that the empty string does the same thing
> both in a config file and on the command line, maybe it's not a
> problem to allow the empty string on the command line. Personally I
> think I'd still prefer to ask the user to use a more explicit syntax.
> Thoughts?
We should be consistent, but I don't have a strong opinion.
Thanks,
Taylor
next prev parent reply other threads:[~2023-08-23 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 3:28 [PATCH] submodule: deprecate --recurse-submodules="" Alex Henrie
2023-08-23 19:37 ` Taylor Blau
2023-08-23 19:53 ` Alex Henrie
2023-08-23 19:57 ` Taylor Blau [this message]
2023-08-23 20:26 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZOZkjoknPJkhgNYf@nand.local \
--to=me@ttaylorr.com \
--cc=Jens.Lehmann@web.de \
--cc=alexhenrie24@gmail.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.
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 NNTP newsgroup(s).