From: Benjamin Schindler <beschindler@gmail.com>
To: git@vger.kernel.org
Subject: gitconfig get out of sync with submodule entries on branch switch
Date: Mon, 30 Jan 2017 17:21:54 +0100 [thread overview]
Message-ID: <0f14df64-1aa2-e671-9785-4e5e0a076ae6@gmail.com> (raw)
Hi
Consider the following usecase: I have the master branch where I have a
submodule A. I create a branch where I rename the submodule to be in the
directory B. After doing all of this, everything looks good.
Now, I switch back to master. The first oddity is, that it fails to
remove the folder B because there are still files in there:
bschindler@metis ~/Projects/submodule_test (testbranch) $ git checkout
master
warning: unable to rmdir other_submodule: Directory not empty
Switched to branch 'master'
Git submodule deinit on B fails because the submodule is not known to
git anymore (after all, the folder B exists only in the other branch). I
can easily just remove the folder B from disk and initialize the
submodule A again, so all seems good.
However, what is not good is that the submodule b is still known in
.git/config. This is in particular a problem for us, because I know a
number of tools which use git config to retrieve the submodule list. Is
it therefore a bug that upon branch switch, the submodule gets
deregistered, but its entry in .git/config remains?
thanks a lot
Benjamin Schindler
P.s. I did not subscribe to the mailing list, please add me at least do
CC. Thanks
next reply other threads:[~2017-01-30 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 16:21 Benjamin Schindler [this message]
2017-01-30 17:51 ` gitconfig get out of sync with submodule entries on branch switch Brandon Williams
2017-01-31 7:46 ` Benjamin Schindler
2017-01-31 22:04 ` Stefan Beller
2017-02-06 10:35 ` Stefan Beller
2017-02-06 12:17 ` Benjamin Schindler
2017-02-08 19:07 ` 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=0f14df64-1aa2-e671-9785-4e5e0a076ae6@gmail.com \
--to=beschindler@gmail.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).