From: Eric Sunshine <sunshine@sunshineco.com>
To: "Дилян Палаузов" <dilyan.palauzov@aegee.org>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Worktree silently deleted on git fetch/gc/log
Date: Thu, 1 Mar 2018 13:09:08 -0500 [thread overview]
Message-ID: <CAPig+cSGJhNR8dapLXN0TU8ZpTqi7m6OQf_cCGmHc9FLGcwNyg@mail.gmail.com> (raw)
In-Reply-To: <aa98f187-4b1a-176d-2a1b-826c995776cd@aegee.org>
On Wed, Feb 28, 2018 at 7:44 AM, Дилян Палаузов
<dilyan.palauzov@aegee.org> wrote:
> 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
next prev parent reply other threads:[~2018-03-01 18:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 12:44 Worktree silently deleted on git fetch/gc/log Дилян Палаузов
2018-03-01 18:09 ` Eric Sunshine [this message]
2018-03-01 19:24 ` Дилян Палаузов
2018-03-01 20:14 ` Eric Sunshine
2018-03-01 23:56 ` Duy Nguyen
2018-03-02 11:34 ` Дилян Палаузов
2018-03-02 11:40 ` Eric Sunshine
2018-03-02 11:53 ` Duy Nguyen
2018-03-03 10:05 ` Eric Sunshine
2018-03-07 10:01 ` Duy Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPig+cSGJhNR8dapLXN0TU8ZpTqi7m6OQf_cCGmHc9FLGcwNyg@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=dilyan.palauzov@aegee.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).