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

Re: Submodule relative URL problems

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jan 13, 2014, 19:55 UTC
Message-ID
<20140113195518.GB18964@google.com>
In-Reply-To
<DAD6CF7D-49F2-4FB5-9EF2-EBAAF86881AA@kcl.ac.uk>
Hi,
Lianheng Tong wrote:
> git clone W1:<path to A on W1>/.git  <path to A on W2>
Interesting.
Thoughts:
 * More typical usage is to clone from a bare repository (A.git), which
   wouldn't have this problem.  But I think your case is worth
   supporting, too.
 * What would you think of putting symlinks in A's .git directory?
	cd A/.git
	ln -s ../B ../C ../D .
 * Perhaps as a special case when the superproject is foo/.git, git
   should treat relative submodule paths as relative to foo/ instead
   of relative to foo/.git/.  I think that would take care of your
   case without breaking existing normal practices, though after the
   patch is made it still wouldn't take care of people using old
   versions of git without that patch.  What do you think?

Thanks, Jonathan

Previous: Lianheng TongNext: Heiko Voigt
Message 2 of 4 in “Submodule relative URL problems”
  1. Lianheng TongJan 13, 2014
  2. Jonathan NiederJan 13, 2014
  3. Heiko VoigtJan 13, 2014
  4. Junio C HamanoJan 13, 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.