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

Re: Git fetch bug in git 2.21+ "Could not access submodule '%s'"

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 14, 2019, 17:56 UTC
Message-ID
<xmqqh86j637g.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<5a58b0eb-0690-c445-dbfd-bd4c5b614629@cisco.com>
"Paolo Pettinato (ppettina)" <ppettina@cisco.com> writes:
Show 10 quoted lines
> Thanks for the reply!
>
> On 14/08/2019 17:40, Junio C Hamano wrote:
>>   Why is the user mucking with
>> that directory in the first place, and isn't the flagging of the
>> situation as an error, done with 26f80ccf ("submodule: migrate
>> get_next_submodule to use repository structs", 2018-11-28), a
>> bugfix?  If not, why not?
>
> Not sure if you're implying here that this is not a bug; I'd say that:
Yeah, sorry for a confused comment.

It does feel strange that the error behaviour depends on what is in the working tree for a "fetch", which is between two $GIT_DIR and does not involve the working tree on the receiving side (that brings us back to my earlier comment in the same message).

Previous: Paolo Pettinato (ppettina)Next: Jeff King
Message 5 of 8 in “Git fetch bug in git 2.21+ "Could not access submodule '%s'"”
  1. Paolo Pettinato (ppettina)Aug 14, 2019
  2. Jeff KingAug 14, 2019
  3. Junio C HamanoAug 14, 2019
  4. Paolo Pettinato (ppettina)Aug 14, 2019
  5. Junio C HamanoAug 14, 2019
  6. Jeff KingAug 14, 2019
  7. get_next_submodule(): format error string as an errorJeff King, Aug 14, 2019
  8. Junio C HamanoAug 14, 2019

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.