From: Jeff King <peff@peff.net>
To: Martin Nicolay <m.nicolay@osm-ag.de>
Cc: git@vger.kernel.org
Subject: Re: missing tags from "git fetch"
Date: Fri, 22 Nov 2019 08:00:20 -0500 [thread overview]
Message-ID: <20191122130020.GA22423@sigill.intra.peff.net> (raw)
In-Reply-To: <alpine.LSU.2.20.1910251150411.2754@cpza.bfz-tzou.qr>
On Fri, Oct 25, 2019 at 12:17:26PM +0200, Martin Nicolay wrote:
> > $ git fetch origin master:refs/remotes/origin/master
>
> I thought it would work, but it works only once. On the second time the ref
> for the remote branch is deleted. It seems git is confused by specifying a
> ref it expect to manage itself.
It seems like a bad interaction with `fetch.prune` (I don't have it set,
and the problem doesn't appear, but if I set it, I can reproduce your
issue).
I'm not sure why, though. It's true that the ref _is_ mentioned in the
configured refspec for origin, but we shouldn't be looking at that
refspec at all (since we have a refspec on the command line).
-Peff
prev parent reply other threads:[~2019-11-22 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 13:10 missing tags from "git fetch" Martin Nicolay
2019-10-02 13:55 ` Jeff King
2019-10-02 15:24 ` Martin Nicolay
2019-10-25 10:17 ` Martin Nicolay
2019-11-22 13:00 ` Jeff King [this message]
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=20191122130020.GA22423@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=m.nicolay@osm-ag.de \
/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).