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

Re: Worktree silently deleted on git fetch/gc/log

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Mar 1, 2018, 18:09 UTC
Message-ID
<CAPig+cSGJhNR8dapLXN0TU8ZpTqi7m6OQf_cCGmHc9FLGcwNyg@mail.gmail.com>
In-Reply-To
<aa98f187-4b1a-176d-2a1b-826c995776cd@aegee.org>

On Wed, Feb 28, 2018 at 7:44 AM, Дилян Палаузов <dilyan.palauzov@aegee.org> wrote:

Show 20 quoted lines
> A (branch master) and
> B (branch g) which is a worktree of the first.
>
> /git/B g>$ git fetch
> [...]
> From https://...
>    13e4c55a0..02655d5fb  g -> origin/g
>    c37a3ca25..bc7888511  master -> origin/master
> Auto packing the repository in background for optimum performance.
> See "git help gc" for manual housekeeping.
> /git/B g<>$ git log -p origin/g
> fatal: Not a git repository: /git/A/.git/worktrees/B
> /git/B$
>
> Please note that on the second last prompt there is <>, so that git-prompt
> has found the neccessary information and this was this was later deleted -
> by 'gc' or 'log'.
>
> What would be the procedure to restore the /git/A/.git/worktrees/B
> structure?
Can you show us (via 'cat') the content of the following files?

/git/B/.git /git/A/.git/worktrees/b/HEAD /git/A/.git/worktrees/b/commondir /git/A/.git/worktrees/b/gitdir

Previous: Дилян ПалаузовNext: Дилян Палаузов
Message 2 of 10 in “Worktree silently deleted on git fetch/gc/log”
  1. Дилян ПалаузовFeb 28, 2018
  2. Eric SunshineMar 1, 2018
  3. Дилян ПалаузовMar 1, 2018
  4. Eric SunshineMar 1, 2018
  5. Duy NguyenMar 1, 2018
  6. Дилян ПалаузовMar 2, 2018
  7. Eric SunshineMar 2, 2018
  8. Duy NguyenMar 2, 2018
  9. Eric SunshineMar 3, 2018
  10. Duy NguyenMar 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.