From: Jeff King <peff@peff.net>
To: Paul Jolly <paul@myitcv.io>
Cc: git@vger.kernel.org
Subject: Re: Change in behaviour in git fetch between 2.18.0 and 2.18.0.547.g1d89318c48
Date: Fri, 10 Aug 2018 14:12:05 -0400 [thread overview]
Message-ID: <20180810181205.GA7516@sigill.intra.peff.net> (raw)
In-Reply-To: <CACoUkn5wXY7924hftXhCXh_N_htWoiaGEV5f7ZEM4-PE57_1oA@mail.gmail.com>
On Fri, Aug 10, 2018 at 07:04:08PM +0100, Paul Jolly wrote:
> I've tried to skim through the archive, but I couldn't find anything
> that describes what I'm seeing. Apologies if that's because I missed
> something/used the wrong search terms, or this is an intentional
> change in behaviour.
>
> Using 2.18.0.547.g1d89318c48, git fetch behaves differently to 2.18.0.
>
> The scenario in which I'm seeing a difference in behaviour is when
> there are (by virtue of the state of my local git repo and the origin,
> remote) pending objects, branch updates etc to fetch from the remote.
> [...]
> Indeed only if I repeat git fetch with 2.18.0.547.g1d89318c48 do I see
> the update to origin/master:
I think this is the bug from:
https://public-inbox.org/git/20180729121900.GA16770@sigill.intra.peff.net/
The fix is in e2842b39f4 (fetch-pack: unify ref in and out param,
2018-08-01), and is currently in the 'next' branch, and marked for
merging to master in the next integration cycle.
-Peff
next prev parent reply other threads:[~2018-08-10 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 18:04 Change in behaviour in git fetch between 2.18.0 and 2.18.0.547.g1d89318c48 Paul Jolly
2018-08-10 18:12 ` Jeff King [this message]
2018-08-10 18:18 ` Paul Jolly
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=20180810181205.GA7516@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=paul@myitcv.io \
/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).