From: Stefan Beller <sbeller@google.com>
To: Jeremy Morton <admin@game-point.net>
Cc: Heiko Voigt <hvoigt@hvoigt.net>,
Junio C Hamano <gitster@pobox.com>,
Jens Lehmann <Jens.Lehmann@web.de>,
Chris Packham <judge.packham@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
mara.kim@vanderbilt.edu, Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [RFC PATCH] clone: add clone.recursesubmodules config option
Date: Wed, 2 Aug 2017 13:34:58 -0700 [thread overview]
Message-ID: <CAGZ79kYy3oBvKXNDnBj01AoOz_JMEg409OTOm+rePz2q+14Hdw@mail.gmail.com> (raw)
In-Reply-To: <598215C8.4000100@game-point.net>
On Wed, Aug 2, 2017 at 11:11 AM, Jeremy Morton <admin@game-point.net> wrote:
> Did this ever get anywhere? If not why not? It would be very useful to me
> to be able to clone recursively by default, especially considering you can't
> use 'alias' to override the existing 'clone' command.
>
Note that there is 3c548de378 (Merge branch 'sb/submodule-blanket-recursive',
2017-06-13), which adds recursing into submodules to a couple of commands.
clone is not one of them, because at that time I thought you'd want to select
explicitly at clone time which submodules you want. Unlike most other commands
that can recurse into submodules, clone supports a pathspec for the recurse
parameter, such that you can express a fine grained selection of submodules
that you are interested in.
I wonder if submodule.recurse is set if we'd just want to recurse into
all submodules for clone? That may have negative consequences though
as people may have forgotten that they set that config a long time ago and then
are surprised to get so many submodules.
next prev parent reply other threads:[~2017-08-02 20:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 18:11 Paper cut bug: Why isn't "git clone xxxx" recursive by default? Mara Kim
2014-06-03 19:52 ` Junio C Hamano
2014-06-03 21:05 ` Junio C Hamano
2014-06-03 22:24 ` Mara Kim
2014-06-04 9:30 ` [RFC PATCH] clone: add clone.recursesubmodules config option Chris Packham
2014-06-04 17:24 ` Junio C Hamano
2014-06-04 19:06 ` Jens Lehmann
2014-06-05 18:18 ` Junio C Hamano
2014-06-05 18:43 ` W. Trevor King
2014-06-06 5:26 ` Heiko Voigt
2017-08-02 18:11 ` Jeremy Morton
2017-08-02 20:34 ` Stefan Beller [this message]
2014-06-04 19:42 ` Heiko Voigt
2014-06-05 7:48 ` Chris Packham
2014-06-06 5:54 ` Heiko Voigt
2014-06-06 16:35 ` Junio C Hamano
2014-06-09 13:17 ` Jens Lehmann
2014-06-09 23:27 ` W. Trevor King
2016-10-03 15:36 ` Jeremy Morton
2016-10-03 17:18 ` Stefan Beller
2016-10-04 11:41 ` Heiko Voigt
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=CAGZ79kYy3oBvKXNDnBj01AoOz_JMEg409OTOm+rePz2q+14Hdw@mail.gmail.com \
--to=sbeller@google.com \
--cc=Jens.Lehmann@web.de \
--cc=admin@game-point.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
--cc=jrnieder@gmail.com \
--cc=judge.packham@gmail.com \
--cc=mara.kim@vanderbilt.edu \
/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).