From: Junio C Hamano <gitster@pobox.com>
To: markusd112@web.de
Cc: git@vger.kernel.org
Subject: Re: missing git documentation for "git clone --recursive"
Date: Mon, 09 Feb 2026 14:01:52 -0800 [thread overview]
Message-ID: <xmqq4inp4lv3.fsf@gitster.g> (raw)
In-Reply-To: <ae4cb197-1edc-44c4-afbb-bbb24df509e8@web.de> (markusd's message of "Mon, 9 Feb 2026 21:34:48 +0100")
markusd112@web.de writes:
> In the git documentation only "--recurse-submodules" is mentioned as
> allowed argument, but not "--recursive".
Correct. Do not use it.
In the early days, we mistakenly used "--recursive" to mean
"--recurse-submodules".
After we realized the mistake, we would have preferred if we could
remove it right away, but in order to avoid breaking existing users,
the command is taught to still notice "--recursive" and behave the
same as "--recurse-submodules", but stopped advertising the former
in "git clone -h" and "git clone --help".
This reminds me. Perhaps we would want to perform an audit for
such OPT_HIDDEN aliases and remove them at the Git 3.0 boundary
(this needs a separate thread to discuss)?
next prev parent reply other threads:[~2026-02-09 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 20:34 missing git documentation for "git clone --recursive" markusd112
2026-02-09 22:01 ` Junio C Hamano [this message]
2026-02-09 22:03 ` D. Ben Knoble
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=xmqq4inp4lv3.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=markusd112@web.de \
/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