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

Re: [PATCH v3] worktree repair: detect relative path in .git file correctly

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 27, 2026, 17:00 UTC
Message-ID
<xmqqse3za47f.fsf@gitster.g>
In-Reply-To
<CAF5D8-vocLWba-rvKxy3WWB1ZHTh1+eRcRWiMqv0M-CX56Y71A@mail.gmail.com>
Yoichi Nakayama <yoichi.nakayama@gmail.com> writes:
> Are you concerned about the lack of explanation in the commit
> message, or about the functional differences between
> `read_gitfile_raw()` and `read_gitfile_gently()`?
Mostly the former, i.e., the commit message too sketchy.

I now understand that these two functions need to be more different than just the _raw() not calling strbuf_realpath() and the other calling strbuf_realpath(). The functional split is fine.

Thanks.
Previous: Yoichi NakayamaNext: Yoichi NAKAYAMA via GitGitGadget
Message 10 of 12 in “worktree repair: detect relative path in .git file correctly”
  1. worktree repair: detect relative path in .git file correctlyYoichi NAKAYAMA via GitGitGadget, Aug 15, 2026
  2. Junio C HamanoAug 17, 2026
  3. Yoichi NakayamaAug 17, 2026
  4. worktree repair: detect relative path in .git file correctlyYoichi NAKAYAMA via GitGitGadget, Aug 20, 2026
  5. Junio C HamanoAug 21, 2026
  6. worktree repair: detect relative path in .git file correctlyYoichi NAKAYAMA via GitGitGadget, Aug 21, 2026
  7. Junio C HamanoAug 21, 2026
  8. Junio C HamanoAug 21, 2026
  9. Yoichi NakayamaAug 27, 2026
  10. Junio C HamanoAug 27, 2026
  11. worktree repair: detect relative path in .git file correctlyYoichi NAKAYAMA via GitGitGadget, Aug 28, 2026
  12. Junio C HamanoAug 28, 2026

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.