From: "Antoine W. Campagna" <awe@frontmatec.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: fatal: could not reset submodule index
Date: Wed, 13 Jun 2018 22:17:58 +0000 [thread overview]
Message-ID: <DB6PR0101MB2344147D4749598823B094F1D97E0@DB6PR0101MB2344.eurprd01.prod.exchangelabs.com> (raw)
Hi,
I would like to add submodules to existing projects.
Some branches would have the submodules and some branches would not.
Since we often switch from one branch to another, I would like the submodules to update automatically so I activate the option submodule.recurse.
But I am experiencing a problem if I do the following:
1. Clone repo, with master containing no submodules
2. Checkout a branch that contains submodules. It results in this error:
fatal: not a git repository: ../.git/modules/submodule
fatal: could not reset submodule index
I think git is trying to update the submodule but the submodule has not yet been initialized (runs "git submodule update" without "--init").
Is there a way to ask git to initialize the submodule automatically ?
Here is the full reproduction instructions:
# Create a repository
mkdir main
cd main
git init
touch main.txt
git add main.txt
git commit -a -m "Initial commit"
cd ..
# Create a second repository
mkdir sub
cd sub
git init
touch sub.txt
git add sub.txt
git commit -a -m "Initial commit of repo sub"
cd ..
# Add the second repository as submodule, on a separate branch
cd main
git branch with-submodule
git checkout with-submodule
git submodule add ../sub sub
git commit -a -m "Add submodule"
# Set main repo back to master branch (without the submodule)
git checkout master
cd ..
# Make a clone and checkout the branch
git clone main clone1
cd clone1
git checkout with-submodule
# Submodule is not automatically updated (sub folder is empty)
git submodule update --init --recursive
# Now the submodule content is there
# But I want to automatically update submodules when checking out a branch
cd ..
# Trying again, adding --recursive during clone
git clone --recursive main clone2
cd clone2
git checkout with-submodule
# Submodule is still not automatically updated (sub folder is empty)
git submodule update --init --recursive
cd ..
# Trying again, adding --recurse-submodules during checkout
git clone --recursive main clone3
cd clone3
git checkout --recurse-submodules with-submodule
# Fails with these error messages :
# fatal: not a git repository: ../.git/modules/sub
# fatal: could not reset submodule index
# It seems like Git tries to update the submodule but without having initialized the submodule
cd ..
# Trying again with submodule.recurse
git config --global submodule.recurse true
git clone main clone4
cd clone4
git checkout with-submodule
# Submodule is still not automatically updated (sub folder is empty)
# It seems like submodule.recurse does not affect git clone
# Trying again with both submodule.recurse and --recursive
git config --global submodule.recurse true
git clone --recursive main clone5
cd clone5
git checkout with-submodule
# Fails with these error messages :
# fatal: not a git repository: ../.git/modules/sub
# fatal: could not reset submodule index
# Same issue as with "git checkout --recurse-submodules"
# I tested this in git-bash on Windows 10
$ git --version
git version 2.17.1.windows.2
# And in Ubuntu in WSL
$ git --version
git version 2.17.1
next reply other threads:[~2018-06-13 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 22:17 Antoine W. Campagna [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-14 18:19 fatal: could not reset submodule index Antoine W. Campagna
2018-06-15 19:47 ` Stefan Beller
2018-06-18 13:57 ` Antoine W. Campagna
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=DB6PR0101MB2344147D4749598823B094F1D97E0@DB6PR0101MB2344.eurprd01.prod.exchangelabs.com \
--to=awe@frontmatec.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.
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).