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

Re: [PATCH v6 7/9] submodule: fix sync handling of relative superproject origin URLs

From
Jon Seymour <jon.seymour@gmail.com>
Date
May 27, 2012, 13:55 UTC
Message-ID
<CAH3AnroV7yWoTp4EW6smmX8T2H1vj8de4dH2Q2y9qiZgBnDS4g@mail.gmail.com>
In-Reply-To
<1338126210-11517-8-git-send-email-jon.seymour@gmail.com>
On Sun, May 27, 2012 at 11:43 PM, Jon Seymour <jon.seymour@gmail.com> wrote:
> When the origin URL of the superproject is itself relative, git sync
> configures the remote.origin.url configuration property of the submodule
> with a path that is relative to the work tree of the super project
sorry! super project -> superproject
> rather than the work tree of the submodule.
>
> To fix this an 'up_path' that navigates from the work tree of the submodule
> to the work tree of the supermodule needs to be prepended to the URL
sorry! supermodule -> superproject.
Previous: Jon SeymourNext: Jon Seymour
Message 9 of 12 in “submodule: improve robustness of path handling”
  1. 0/9 submodule: improve robustness of path handlingJon Seymour, May 27, 2012
  2. 1/9 submodule: additional regression tests for relative URLsJon Seymour, May 27, 2012
  3. 2/9 submodule: document failure to detect invalid submodule URLsJon Seymour, May 27, 2012
  4. 3/9 submodule: document failure to handle relative superproject origin URLsJon Seymour, May 27, 2012
  5. 4/9 submodule: document failure to handle improperly normalized remote origin URLsJon Seymour, May 27, 2012
  6. 5/9 submodule: extract normalize_path into standalone functionJon Seymour, May 27, 2012
  7. 6/9 submodule: fix detection of invalid submodule URLJon Seymour, May 27, 2012
  8. 7/9 submodule: fix sync handling of relative superproject origin URLsJon Seymour, May 27, 2012
  9. Jon SeymourMay 27, 2012
  10. 8/9 submodule: fix handling of denormalized superproject origin URLsJon Seymour, May 27, 2012
  11. Jon SeymourMay 27, 2012
  12. 9/9 submodule: fix normalization to handle repeated ./Jon Seymour, May 27, 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.