From: Junio C Hamano <gitster@pobox.com>
To: Chris Wilson <chris+gitscm@aptivate.org>
Cc: git@vger.kernel.org
Subject: Re: Possible bug: Git submodules can get into broken state
Date: Fri, 05 Apr 2013 09:51:31 -0700 [thread overview]
Message-ID: <7vmwtcdip8.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1304042302550.965@lap-x201.fen.aptivate.org> (Chris Wilson's message of "Thu, 4 Apr 2013 23:07:19 +0100 (BST)")
Chris Wilson <chris+gitscm@aptivate.org> writes:
> They fixed it by checking in a rectified .gitmodules file.
>
> In the mean time, I ran git submodule init, and now I've ended up in a
> situation where git submodule update doesn't work, and there's no
> submodule command to fix it, so I have to remove the broken submodules
> from .git/config.
>
>> and the configuration mechanism is the way to use custom URL in
>> place of it.
>
> I don't want to use a custom URL, I want to use the URL which is now
> in .gitmodules.
Then don't call it a "custom URL" ;-).
Isn't your problem that the old, broken one is now in your config,
and you want to update that with a corrected one? How you learned
which one is correct does not really matter---you may learned it out
of band by looking at upstream's gitweb, or by running "git fetch"
in the superproject again and looking at the updated .gitmodules
file. The configuration mechanism has a way to update that entry.
> Could submodule init at least change the URLs of submodules which are
> not checked out? (e.g. because they couldn't be)?
Perhaps "submodule deinit" might be what you are looking for, but I
dunno.
next prev parent reply other threads:[~2013-04-06 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 17:10 Possible bug: Git submodules can get into broken state Chris Wilson
2013-04-04 18:30 ` Junio C Hamano
2013-04-04 20:40 ` Chris Wilson
2013-04-04 21:07 ` Junio C Hamano
2013-04-04 22:07 ` Chris Wilson
2013-04-05 16:51 ` Junio C Hamano [this message]
2013-04-04 19:56 ` Jens Lehmann
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=7vmwtcdip8.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=chris+gitscm@aptivate.org \
--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.
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).