On Wed, Apr 23, 2008 at 9:27 AM, Ping Yin <pkufranky@xxxxxxxxx> wrote: > > On Wed, Apr 23, 2008 at 1:28 AM, Johannes Schindelin > <Johannes.Schindelin@xxxxxx> wrote: > > Hi, > > > > > > On Wed, 23 Apr 2008, Ping Yin wrote: > > > > > If we go back to a old HEAD or switch to another branch with changed > > > path for a submodule, what should 'git submodule update' do? I think > > > entries in .gitmodules should take precedence. > > > > Literally the most common reason for a _different_ .gitmodules in an older > > revision is that the repository was moved to another machine. > > > > In this case, your suggestion is actively wrong. > > > Another common reason is the adjustment of repository directory in the > central environment I'm wrong, this is the case that *url* changes. > so i said *path*, not *url*. I agree what Josef said in the the > following reply: "It makes no sense to have submodule path > configuration in .git/config, as it has to be in sync with the current > commit". So it should be bettter to store path info only in > .gitmodules instead of $GIT_DIR/config > The case that *path* changes is the submodule is moved to a new path in some commit. But it is a very rare case. -- Ping Yin -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
