Re: Should `git remote show` display excluded branches as to-be-fetched?

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 10, 2022, 17:08 UTC
Message-ID: <xmqq1qvwfntm.fsf@gitster.g>
In-Reply-To: <CAChcVumTgNqRTt=EtThXiw9ga=W9WC-uS0XOkz7T+TbtGKeU+w@mail.gmail.com>

Pavel Rappo <pavel.rappo@gmail.com> writes:

Show 5 quoted lines

> Here's a console session:
>
>   % git config --get-all remote.jdk19.fetch
>   +refs/heads/*:refs/remotes/jdk19/*
>   ^refs/heads/pr/*

Thanks

"Negative refspecs" is relatively new feature introduced in c0192df6 (refspec: add support for negative refspecs, 2020-09-30), so it would not be so surprising if it still had some surprising behaviour ;-)

Jacob, care to take a look?

Show 23 quoted lines

>   % git remote show jdk19
>
>   * remote jdk19
>     Fetch URL: git@github.com:openjdk/jdk19.git
>     Push  URL: git@github.com:openjdk/jdk19.git
>     HEAD branch: master
>     Remote branches:
>       master tracked
>       pr/1   new (next fetch will store in remotes/jdk19)
>       pr/2   new (next fetch will store in remotes/jdk19)
>       pr/3   new (next fetch will store in remotes/jdk19)
>     Local ref configured for 'git push':
>       master pushes to master (fast-forwardable)
>
> I would naively expect the pr/1, pr/2, and pr/3 branches to be either:
>
> - not displayed, or better
> - displayed with a hint that they won't be fetched (since they match a
> _negative_ refspec, which is the second line in the `git config`
> output above)
>
> Thanks,
> -Pavel