From: Junio C Hamano <gitster@pobox.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: Duy Nguyen <pclouds@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: git fetch <remote> <branch> behaves weirdely when run in a worktree
Date: Tue, 25 Sep 2018 14:40:17 -0700 [thread overview]
Message-ID: <xmqqpnx1ntmm.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <fa6d37b850177f7f2ba31c596d5986962eaf7382.camel@gmail.com> (Kaartic Sivaraam's message of "Wed, 26 Sep 2018 00:14:19 +0530")
Kaartic Sivaraam <kaartic.sivaraam@gmail.com> writes:
>> 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: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
> ...
That looks like fetching only the 'next' branch and nothing else to
me.
Perhaps your script is referring to a variable whose assignment is
misspelled and invoking
git fetch $origin $branch
and you are expecting the $branch variable to have string 'next' but
due to some bugs it is empty somehow? That explains why sometimes
(i.e. when $branch does not get the value you expect it to have) the
script fetches everything and some other times (i.e. when $branch
does get the right value) the script fetches only the named branch.
next prev parent reply other threads:[~2018-09-25 21:40 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
2018-09-25 21:40 ` Junio C Hamano [this message]
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=xmqqpnx1ntmm.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@gmail.com \
--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).