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

Re: git push requires a worktree?

From
Duy Nguyen <pclouds@gmail.com>
Date
May 30, 2018, 18:50 UTC
Message-ID
<CACsJy8Dy6Ft7jnj2SFz_0uLSxv9muujY_0nTvFbi3XGMEGFKgA@mail.gmail.com>
In-Reply-To
<CAGZ79kaT2KM0cZOSEXMpnr53TxUdH=gSbyQaGdBw1wEGnkK2Kw@mail.gmail.com>
On Wed, May 30, 2018 at 7:32 PM, Stefan Beller <sbeller@google.com> wrote:
> * the setup code for commands that do not have the
>   NEED_WORK_TREE flag in git.c

Unless it's very urgent, I can fix it later (and hopefully soon-ish). The problem is definitely not with setting core.worktree but with too eagerly chdir() when you don't need it. We also have another problem (chdir'ing too late) in the same area that led to the introduction of chdir-notify. If I'm successful in killing chdir-notify by chdir at the right time and with the right condition, then it should fix this as well. I'm pretty close to it, I think.

-- 
Duy
Previous: Stefan Beller
Message 3 of 3 in “git push requires a worktree?”
  1. David TurnerMay 30, 2018
  2. Stefan BellerMay 30, 2018
  3. Duy NguyenMay 30, 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.