Re: Change in behaviour in git fetch between 2.18.0 and 2.18.0.547.g1d89318c48

From: Jeff King <peff@peff.net>
Date: Aug 10, 2018, 18:12 UTC
Message-ID: <20180810181205.GA7516@sigill.intra.peff.net>
In-Reply-To: <CACoUkn5wXY7924hftXhCXh_N_htWoiaGEV5f7ZEM4-PE57_1oA@mail.gmail.com>

On Fri, Aug 10, 2018 at 07:04:08PM +0100, Paul Jolly wrote:

Show 13 quoted lines

> 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