From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git fetch <remote> <branch> behaves weirdely when run in a worktree
Date: Wed, 26 Sep 2018 00:14:19 +0530 [thread overview]
Message-ID: <fa6d37b850177f7f2ba31c596d5986962eaf7382.camel@gmail.com> (raw)
In-Reply-To: <CACsJy8D_37U+4sb7tb8KqGM=_3CRrTaZX1ZE9VqDVrYJT-AhnA@mail.gmail.com>
On Mon, 2018-09-24 at 17:17 +0200, Duy Nguyen wrote:
> On Sun, Sep 23, 2018 at 10:19 PM Kaartic Sivaraam
> <kaartic.sivaraam@gmail.com> wrote:
>
> Yes, some bugs. It behaves correctly for me. There must be something
> strange that triggers this. What's your "git worktree list" (iow
> anything strange there, duplicate worktrees perhaps)?
Nothing seems strange in the list.
$ git worktree list
$COMMON_ROOT/git 01d371f741 (detached HEAD)
$COMMON_ROOT/git-next cfa73bbfcb (detached HEAD)
$COMMON_ROOT/git-next-build-automate 01d371f741 (detached HEAD)
$COMMON_ROOT/git-pu 363c5c06bb (detached HEAD)
Note: I sanitized the path in which the git worktrees (including the
main worktree) is present as $COMMON_ROOT.
> Also please try
> "git fetch" again with GIT_TRACE=1 and GIT_TRACE_SETUP=1. Hopefully we
> could catch something with that.
$ GIT_TRACE_SETUP=1 GIT_TRACE=1 git fetch origin next
23:10:26.049785 trace.c:377 setup: git_dir: $COMMON_ROOT/git/.git/worktrees/git-next-build-automate
23:10:26.049868 trace.c:378 setup: git_common_dir: $COMMON_ROOT/git/.git
23:10:26.049901 trace.c:379 setup: worktree: $COMMON_ROOT/git-next-build-automate
23:10:26.049922 trace.c:380 setup: cwd: $COMMON_ROOT/git-next-build-automate
23:10:26.049941 trace.c:381 setup: prefix: (null)
23:10:26.049955 git.c:415 trace: built-in: git fetch origin next
23:10:26.051033 run-command.c:637 trace: run_command: git-remote-https origin https://github.com/git/git.git
23:10:28.366526 run-command.c:637 trace: run_command: git rev-list --objects --stdin --not --all --quiet
23:10:28.400979 run-command.c:637 trace: run_command: git rev-list --objects --stdin --not --all --quiet
23:10:28.402745 trace.c:377 setup: git_dir: $COMMON_ROOT/git/.git/worktrees/git-next-build-automate
23:10:28.402787 trace.c:378 setup: git_common_dir: $COMMON_ROOT/git/.git
23:10:28.402793 trace.c:379 setup: worktree: $COMMON_ROOT/git-next-build-automate
23:10:28.402798 trace.c:380 setup: cwd: $COMMON_ROOT/git-next-build-automate
23:10:28.402802 trace.c:381 setup: prefix: (null)
23:10:28.402815 git.c:415 trace: built-in: git rev-list --objects --stdin --not --all --quiet
From https://github.com/git/git
* branch next -> FETCH_HEAD
23:10:28.437350 run-command.c:1553 run_processes_parallel: preparing to run up to 1 tasks
23:10:28.437481 run-command.c:1585 run_processes_parallel: done
23:10:28.437763 run-command.c:637 trace: run_command: git gc --auto
23:10:28.439608 trace.c:377 setup: git_dir: $COMMON_ROOT/git/.git/worktrees/git-next-build-automate
23:10:28.439655 trace.c:378 setup: git_common_dir: $COMMON_ROOT/git/.git
23:10:28.439667 trace.c:379 setup: worktree: $COMMON_ROOT/git-next-build-automate
23:10:28.439677 trace.c:380 setup: cwd: $COMMON_ROOT/git-next-build-automate
23:10:28.439687 trace.c:381 setup: prefix: (null)
23:10:28.439699 git.c:415 trace: built-in: git gc --auto
HTH,
Sivaraam
next prev parent reply other threads:[~2018-09-25 18:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 20:09 git fetch <remote> <branch> behaves weirdely when run in a worktree Kaartic Sivaraam
2018-09-24 15:17 ` Duy Nguyen
2018-09-25 18:44 ` Kaartic Sivaraam [this message]
2018-09-25 21:40 ` Junio C Hamano
2018-09-26 3:37 ` Kaartic Sivaraam
2018-09-26 4:46 ` Kaartic Sivaraam
2018-09-26 15:24 ` Duy Nguyen
2018-09-26 16:09 ` Duy Nguyen
2018-09-26 17:05 ` Junio C Hamano
2018-10-02 18:43 ` Kaartic Sivaraam
2018-10-04 6:54 ` Kaartic Sivaraam
2018-10-04 7:00 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa6d37b850177f7f2ba31c596d5986962eaf7382.camel@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
/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.
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 NNTP newsgroup(s).