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

Re: reflogs and worktrees?

From
Duy Nguyen <pclouds@gmail.com>
Date
Jul 5, 2016, 15:59 UTC
Message-ID
<CACsJy8A=_0RfMsDkqyeyro3Xw3NbS4qU0bkVAkapky52jphH7w@mail.gmail.com>
In-Reply-To
<alpine.DEB.2.20.1607051704490.8378@virtualbox>

On Tue, Jul 5, 2016 at 5:07 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

> Hi Duy,
>
> ever since I started working extensively with worktrees, I end up with
> these funny gc problems, like broken links and stale reflogs.

Yeah we have problem with gc not traversing all worktree refs. I had something that could fix it temporarily [1] but the decision was to wait for refs code to support new "worktree storage" so that we can walk worktree refs properly, then fix gc [2]. We should get pretty close to that point after [3] lands.

[1] http://thread.gmane.org/gmane.comp.version-control.git/295961/focus=296076 [2] http://thread.gmane.org/gmane.comp.version-control.git/295961/focus=296219 [3] http://thread.gmane.org/gmane.comp.version-control.git/296409

> Is it maybe possible that the reflogs (which are per-worktree now) are not
> traversed completely when gc'ing (which is *not* per-worktree)?
-- 
Duy
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 2 of 3 in “reflogs and worktrees?”
  1. Johannes SchindelinJul 5, 2016
  2. Duy NguyenJul 5, 2016
  3. Johannes SchindelinJul 9, 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.