Re: What's cooking in git.git (topics)

From: Ping Yin <pkufranky@gmail.com>
Date: Apr 23, 2008, 01:27 UTC
Message-ID: <46dff0320804221827g6579919fid69d581256de90e1@mail.gmail.com>
In-Reply-To: <alpine.DEB.1.00.0804221827330.4460@eeepc-johanness>

On Wed, Apr 23, 2008 at 1:28 AM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 14 quoted lines

> 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 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

-- 
Ping Yin