git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Relative submodule URLs, and forks that haven't forked the submodule

From
CBCharles Brossollet <chbrosso@lltech.fr>
Date
Jun 11, 2014, 10:15 UTC
Message-ID
<E4E16320-06C4-40C5-B561-8DAD720F0946@lltech.fr>
Hi,
I'm banging my head on this problem: I have a central repo cloned by SSH, and a fork on the same server. The central remote is origin, and the fork is chbrosso-wip.

$ git remote -v | grep origin origin chbrosso@lltech:/git/lightct.git (fetch) origin chbrosso@lltech:/git/lightct.git (push)

$ git remote -v | grep chbrosso-wip chbrosso-wip chbrosso@lltech:~/prog/git/lightct.git (fetch) chbrosso-wip chbrosso@lltech:~/prog/git/lightct.git (push)

On a local working copy, fetched my fork and checked out a remote branch out of it. Its remote-tracking branch is on the fork.
$ git branch -vv | grep \*
* actor                         d98ec24 [chbrosso-wip/actor] (commit msg)
Now, submodules for this repo have relative URLs. And this is where the problem begins, because the submodule isn't forked, but resides only in origin.
But this shouldn't cause any problem, right? The docs says that if relative URL are used, they resolve using the origin URL. First issue, it's not the case:
$ cat .gitmodules
[submodule "motors"]
        path = motors
        url = ../motors.git
        branch = master
$ git submodule init motors
Submodule 'motors' (chbrosso@lltech:~/prog/git/motors.git) registered for path 'motors'
Here the submodule is registered on my fork, which doesn't exist, and it's wrong with what the documentation says.
Fine, I'll edit the .git/config entry to make it point to origin:
$ git config submodule.motors.url chbrosso@lltech:/git/motors.git

$ git config submodule.motors.url chbrosso@lltech:/git/motors.git

$ ssh chbrosso@lltech "if [ -d /git/motors.git ]; then echo 'ok'; fi" Password: ok

So the submodule's url is changed, and points to a correct path, let's update so that I can work

$ git submodule update motors Password: fatal: '~/prog/git/motors.git' does not appear to be a git repository fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists. Unable to fetch in submodule path 'motors'

That's right, it is still the old url, and I can't have my submodule! Can someone explain what's going on? And how can I get my submodule in the working copy?

git version 1.9.2.msysgit.0 on Windows 7 SP1 64 bit

Thanks, —- Charles

Next: Fredrik Gustafsson
Message 1 of 4 in “Relative submodule URLs, and forks that haven't forked the submodule”
  1. Charles BrossolletJun 11, 2014
  2. Fredrik GustafssonJun 12, 2014
  3. Charles BrossolletJun 12, 2014
  4. W. Trevor KingJun 12, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.