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

> I think this is the bug from: > > https://public-inbox.org/git/20180729121900.ga16...@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

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

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. > >

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

Hi, 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