From: Leandro Lucarella <leandro.lucarella@sociomantic.com>
To: <git@vger.kernel.org>
Subject: Getting "The following submodule paths contain changes that can not be found on any remote" when they are in the remote
Date: Tue, 23 Aug 2016 20:34:46 +0200 [thread overview]
Message-ID: <20160823203446.40abfd37@labs-064.localdomain> (raw)
Hi, I'm getting very often, but not always, with many different
projects using submodules, the message:
The following submodule paths contain changes that can
not be found on any remote:
<module>
Please try
git push --recurse-submodules=on-demand
or cd to the path and use
git push
to push them to a remote.
fatal: Aborting.
This even happens after doing a:
git submodule deinit <module>
rm -fr <module>
rm -fr .git/modules/<module>
git submodule update --init
So I am getting the reference from the remote, but when pushing a new
change (that doesn't touch the submodules) I keep getting this error.
I tried to get more information about why this is happening but I
couldn't. Googling didn't help either, so I'm resorting to ask here.
I would also like to report a tiny bug, when using push --quiet, I do
get all the message above except for the <module> name, which is quite
confusing.
$ git --version
git version 2.9.3
(running under Ubuntu 14.04)
Please CC me, and thanks a lot in advance!
--
Leandro Lucarella
Technical Development Lead
Sociomantic Labs GmbH <http://www.sociomantic.com>
next reply other threads:[~2016-08-23 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 18:34 Leandro Lucarella [this message]
2016-08-23 18:38 ` Getting "The following submodule paths contain changes that can not be found on any remote" when they are in the remote Leandro Lucarella
2016-08-23 23:30 ` Stefan Beller
2016-08-23 21:26 ` Stefan Beller
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=20160823203446.40abfd37@labs-064.localdomain \
--to=leandro.lucarella@sociomantic.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).