From: Jeff King <peff@peff.net>
To: Vadim Eisenberg <VADIME@il.ibm.com>
Cc: Stefan Beller <sbeller@google.com>, git@vger.kernel.org
Subject: Re: [BUG REPORT] git 2.9.0 clone --recursive fails on cloning a submodule
Date: Sun, 19 Jun 2016 10:46:28 -0400 [thread overview]
Message-ID: <20160619144628.GA7402@sigill.intra.peff.net> (raw)
In-Reply-To: <OFC46A8782.5F47CDBA-ONC2257FD7.00475209-C2257FD7.00483117@notes.na.collabserv.com>
On Sun, Jun 19, 2016 at 04:07:41PM +0300, Vadim Eisenberg wrote:
> The problem is with other tools that use git, like Swift Package Manager -
> https://swift.org/package-manager/.
> Versions of git before 2.9.0 have no option --no-shallow-submodules. So
> the tools that use git would have to check if the version of git is
> greater than or equal 2.9.0 to know to specify that option.
Oh, I agree it's something we should treat as a regression. Using
`--no-shallow-submodules` is just a workaround.
-Peff
next prev parent reply other threads:[~2016-06-19 14:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OFC76C15DC.FC882C57-ONC2257FD7.00261552-C2257FD7.002660FC@LocalDomain>
2016-06-19 7:17 ` [BUG REPORT] git 2.9.0 clone --recursive fails on cloning a submodule Vadim Eisenberg
2016-06-19 10:00 ` Jeff King
2016-06-19 13:07 ` Vadim Eisenberg
2016-06-19 14:46 ` Jeff King [this message]
2016-06-19 20:51 ` Junio C Hamano
2016-06-20 0:13 ` Jeff King
2016-06-20 1:09 ` Stefan Beller
2016-06-20 3:01 ` Vadim Eisenberg
2016-06-20 5:31 ` Dennis Kaarsemaker
2016-06-20 10:02 ` Jeff King
2016-06-20 16:59 ` [PATCH] shallow clone to not imply shallow submodules Stefan Beller
2016-06-20 17:13 ` Jeff King
2016-06-20 17:14 ` Stefan Beller
2016-06-20 17:18 ` Jeff King
2017-04-19 11:30 ` [BUG REPORT] git 2.9.0 clone --recursive fails on cloning a submodule Ævar Arnfjörð Bjarmason
2017-04-19 18:54 ` Stefan Beller
2016-06-21 16:48 ` Duy Nguyen
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=20160619144628.GA7402@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=VADIME@il.ibm.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.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).