From: Junio C Hamano <gitster@pobox.com>
To: jyotish kumar <jyotishkumar725015@gmail.com>
Cc: git@vger.kernel.org, Harald Nordgren <haraldnordgren@gmail.com>
Subject: Re: [RFC] pull: custom fetch refspecs and fork-point lookup
Date: Wed, 14 Oct 2026 12:07:42 -0700 [thread overview]
Message-ID: <xmqq5wz4rthd.fsf@gitster.g> (raw)
In-Reply-To: <CAGjZMyTQt2XEF69pJWHA=diRjoidixGs48E1vA0ytGUgZYOZNQ@mail.gmail.com> (jyotish kumar's message of "Tue, 13 Oct 2026 21:31:09 +0530")
jyotish kumar <jyotishkumar725015@gmail.com> writes:
> While reading `builtin/pull.c`, I came across a FIXME in
> `get_tracking_branch()` concerning the assumption that remote branches
> follow the default mapping from `refs/heads/<branch>` to
> `refs/remotes/<remote>/<branch>`.
> ...
> Does this analysis sound correct? I would appreciate feedback on
> whether this is a real issue and whether resolving the configured
> fetch mapping would be the right direction to address it.
The reason the "FIXME" you noticed exists is that the assumption the
code makes is broken. Assuming that refs/remotes/<remote>/<branch>
tracks <branch> from <remote> would break when a customized fetch
refspec is used.
I vaguely recall mentioning a similar "map between a remote-tracking
branch and a branch at the remote" issue while discussing a recent
work by Harald to narrow a "git fetch" that does not specify what to
fetch, but I cannot find a mailing list archive reference, sorry.
next prev parent reply other threads:[~2026-10-14 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 16:01 [RFC] pull: custom fetch refspecs and fork-point lookup jyotish kumar
2026-10-14 19:07 ` Junio C Hamano [this message]
2026-10-15 7:17 ` Harald Nordgren
2026-10-15 10:46 ` jyotish kumar
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=xmqq5wz4rthd.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=haraldnordgren@gmail.com \
--cc=jyotishkumar725015@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