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

Re: [PATCH v3 2/4] submodule: support superproject origin URLs of the form ./foo/bar or ../foo/bar

From
Jon Seymour <jon.seymour@gmail.com>
Date
May 21, 2012, 22:20 UTC
Message-ID
<CAH3AnrrEnLEnN=EgzaDjFtN6r9RBpTmPNTX96QiMtGz9J12eCQ@mail.gmail.com>
In-Reply-To
<CAH3AnrqBeD3JisjoK2dqnPWcBAFTxB5NYgRkfSPqb-CS8a0hsw@mail.gmail.com>
On Tue, May 22, 2012 at 2:35 AM, Jon Seymour <jon.seymour@gmail.com> wrote:
Show 8 quoted lines
> On Mon, May 21, 2012 at 11:31 PM, Jon Seymour <jon.seymour@gmail.com> wrote:
>
> Mmmm. Better hold off on this one for the moment, I have detected a
> break during a subsequent git submodule update that my selection of
> regression tests didn't pick up. The issue is that the URL used for
> cloning the submodule during the update is now not correct.
>
> jon.

I guess the issue here is that whereas the origin url of the submodule (as in remote.origin.url in the submodule) should be relative to the submodule's working tree, it might actually be better to keep submodule.{modulename}.url relative to the working directory of superproject (which is current behaviour).

Thoughts?
jon.
Previous: Jon SeymourNext: Jon Seymour
Message 4 of 6 in “submodule: verify support for superproject origin URLs of the form ./foo/bar or ../foo/bar”
  1. 1/4 submodule: verify support for superproject origin URLs of the form ./foo/bar or ../foo/barJon Seymour, May 21, 2012
  2. 2/4 submodule: support superproject origin URLs of the form ./foo/bar or ../foo/barJon Seymour, May 21, 2012
  3. Jon SeymourMay 21, 2012
  4. Jon SeymourMay 21, 2012
  5. 3/4 submodule: verify support for superproject URLs of the form foo/bar.Jon Seymour, May 21, 2012
  6. 4/4 submodule: support superproject origin URLs of the form foo/barJon Seymour, May 21, 2012

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.