From: Stefan Beller <sbeller@google.com>
To: Leandro Lucarella <leandro.lucarella@sociomantic.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: 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 16:30:38 -0700 [thread overview]
Message-ID: <CAGZ79kZ7LHx6sWdMWzv3d1SgS_PPBdVu07tGWhz14tWmAb2eJw@mail.gmail.com> (raw)
In-Reply-To: <20160823203819.2dfa513c@labs-064.localdomain>
On Tue, Aug 23, 2016 at 11:38 AM, Leandro Lucarella
<leandro.lucarella@sociomantic.com> wrote:
> On Tue, 23 Aug 2016 20:34:46 +0200
> Leandro Lucarella <leandro.lucarella@sociomantic.com> wrote:
>> This even happens after doing a:
>>
>> git submodule deinit <module>
>> rm -fr <module>
>> rm -fr .git/modules/<module>
>> git submodule update --init
>
> One more thing, doing a clean new clone seems to work, but I have this
> issue in many many repos, which are old clones, from before Git had the
> ability to check for submodules. Could it be some incompatibility in
> old clones with this? Is there anything I can look for in the .git/
> directory or elsewhere to fix them?
Check if push.recurseSubmodules is set?
>
> Thanks again!
>
> --
> Leandro Lucarella
> Technical Development Lead
> Sociomantic Labs GmbH <http://www.sociomantic.com>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-08-23 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 18:34 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 18:38 ` Leandro Lucarella
2016-08-23 23:30 ` Stefan Beller [this message]
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=CAGZ79kZ7LHx6sWdMWzv3d1SgS_PPBdVu07tGWhz14tWmAb2eJw@mail.gmail.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=leandro.lucarella@sociomantic.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.
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).