From: Jens Lehmann <Jens.Lehmann@web.de>
To: Howard Miller <howard@e-learndesign.co.uk>
Cc: git@vger.kernel.org
Subject: Re: Problems after deleting submodule
Date: Tue, 18 Oct 2011 21:56:16 +0200 [thread overview]
Message-ID: <4E9DD9E0.80808@web.de> (raw)
In-Reply-To: <CAHVO_90UN_nNDbqxM2TkUjo_qfVhLgjUJoZTmYi6rsLnRMOUFg@mail.gmail.com>
Am 18.10.2011 13:54, schrieb Howard Miller:
> I included a submodule in my project then decided I didn't like
> submodules and deleted it again. I followed the advice of delting
> .gitmodules, the bit from .git/config and then git rm'ing the
> submodule. Seemed to work. I then copied files with the same directory
> name into where the submodule was. However, I can't add them.
>
> Doing git add /path/to/old/submodule - does nothing, files are not
> staged, no error messages no nothing.
> If I try to git rm /path/to/old/submodule - it just says 'did not
> match any files'.
>
> It simply does not seem to want to add anything to the old submodule
> location. I had a grep around and could not see any obvious references
> in the repo.
>
> I'm a bit stuck... any suggestions for things I can try much appreciated.
Looks like the gitlink entry of the submodule is still there. I assume
git ls-files --stage | grep 160000
still shows the submodule? That would make it impossible to add anything
in the former submodule directory.
When I delete .gitmodules and the .git/config entry and do a
git rm sub/
I get
fatal: pathspec 'sub/' did not match any files
If I omit the trailing slash it is:
fatal: git rm: 'sub': Is a directory
I have to do a
rm -rf sub
followed by
git rm sub
to get everything cleaned up.
Does that help you?
next prev parent reply other threads:[~2011-10-18 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 11:54 Problems after deleting submodule Howard Miller
2011-10-18 19:56 ` Jens Lehmann [this message]
2011-10-19 10:23 ` Howard Miller
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=4E9DD9E0.80808@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=howard@e-learndesign.co.uk \
/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).