git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Fredrik Gustafsson <iveqy@iveqy.com>
Cc: Manuel Koller <koller.manuel@gmail.com>, <git@vger.kernel.org>,
	Jens Lehmann <Jens.Lehmann@web.de>,
	Heiko Voigt <hvoigt@hvoigt.net>
Subject: Re: Git Submodule Problem - Bug?
Date: Tue, 29 Nov 2011 11:25:41 +0100	[thread overview]
Message-ID: <201111291125.41943.trast@student.ethz.ch> (raw)
In-Reply-To: <20111129101546.GB2829@kolya>

Fredrik Gustafsson wrote:
> > [removing a submodule and adding another under the same name
> > confuses git]
> 
> This is something I did not thought about when writing that patch. The
> reason that this fails is that the part when the first submodule is
> removed is no longer complete (as intended). Before this patch
>      git config --remove-section submodule.sub &&
>      git rm .gitmodules &&
>      rm -rf sub &&
> Did remove all the data associated with the submodule. That's no longer
> the case.

So maybe the right questions to ask would be: what's the *official*
way of removing a submodule completely?  Do we support overwriting
submodules in the way Manuel wanted to?  Why not? :-)

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2011-11-29 10:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28 17:13 Git Submodule Problem - Bug? Manuel Koller
2011-11-29  9:24 ` Thomas Rast
2011-11-29 10:15   ` Fredrik Gustafsson
2011-11-29 10:25     ` Thomas Rast [this message]
2011-11-29 10:41       ` Fredrik Gustafsson
2011-11-29 17:42         ` Jens Lehmann
2011-11-29 18:15           ` Manuel Koller
2011-11-29 19:21             ` Junio C Hamano
2011-11-29 22:03           ` Heiko Voigt
2011-12-07  8:21             ` Manuel Koller
2011-12-07 21: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=201111291125.41943.trast@student.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=Jens.Lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=hvoigt@hvoigt.net \
    --cc=iveqy@iveqy.com \
    --cc=koller.manuel@gmail.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.
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).