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

Re: Old submodules broken in 2.19rc1 and 2.19rc2

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Sep 7, 2018, 20:20 UTC
Message-ID
<20180907202007.GC103699@aiede.svl.corp.google.com>
In-Reply-To
<CAGZ79kaVQ0T=acpviOoD+8XVxYsefNkO7c5d+d0Wc0iCbr2Evw@mail.gmail.com>
Stefan Beller wrote:
> On Fri, Sep 7, 2018 at 2:53 AM Allan Sandfeld Jensen <allan.jensen@qt.io> wrote:
>>                       A "git submodule update --recursive" command wil fail
>> for each submodule with a line saying "fatal: could not open
>> '<submodule>/.git' for writing> Is a directory.
[...]
> I have the suspicion that e98317508c0 (submodule:
> ensure core.worktree is set after update, 2018-06-18)
> might be the offender.
Oh!  That seems likely.

Allan, output from "strace -f git submodule update --init" would also be interesting.

Jonathan
Previous: Stefan BellerNext: Jonathan Nieder
Message 6 of 14 in “Old submodules broken in 2.19rc1 and 2.19rc2”
  1. Allan Sandfeld JensenSep 7, 2018
  2. Jeff KingSep 7, 2018
  3. Allan Sandfeld JensenSep 7, 2018
  4. Jonathan NiederSep 7, 2018
  5. Stefan BellerSep 7, 2018
  6. Jonathan NiederSep 7, 2018
  7. Jonathan NiederSep 7, 2018
  8. Stefan BellerSep 7, 2018
  9. Revert "Merge branch 'sb/submodule-core-worktree'" (was Re: Old submodules broken in 2.19rc1 and 2.19rc2)Jonathan Nieder, Sep 8, 2018
  10. Junio C HamanoSep 8, 2018
  11. Johannes SixtSep 8, 2018
  12. Stefan BellerSep 10, 2018
  13. Junio C HamanoSep 11, 2018
  14. Allan Sandfeld JensenSep 7, 2018

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.