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

Re: Git mv -- submodule -- recursive

From
Stefan Beller <sbeller@google.com>
Date
Jun 27, 2016, 16:57 UTC
Message-ID
<CAGZ79kYKBxL4xLyySALBv_-gqkss9_iCk-qSc4T7u7fKDMOFWw@mail.gmail.com>
In-Reply-To
<CAOG-3GJdH5q9fdj+7zdEv-UUZMTAnunZu1PRJYjFNV360r6+sQ@mail.gmail.com>
On Sun, Jun 26, 2016 at 11:01 PM, Bart Bogaerts <bartbogaerts@gmail.com> wrote:
Show 12 quoted lines
> With a repo structured as follows
>
> main-files
> |- submod
>     |- subsubmodule
>
> git mv submod newlocation
>
> does not do what it is supposed to do. It actually breaks the git repository.
> It can be fixed easily.
> A complete description of the bug, including a workaround, can be found on
> http://stackoverflow.com/q/32782382/2274140

Which version of Git are you using? I think this is fixed in a127331cd81233 (mv: allow moving nested submodules, 2016-04-19), which is first included in v2.8.3 (or v2.9 and later).

Thanks, Stefan

Show 7 quoted lines
>
> --
> Bart Bogaerts
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous: Bart BogaertsNext: Bart Bogaerts
Message 2 of 4 in “Git mv -- submodule -- recursive”
  1. Bart BogaertsJun 27, 2016
  2. Stefan BellerJun 27, 2016
  3. Bart BogaertsJun 27, 2016
  4. Stefan BellerJun 27, 2016

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.