git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
PRPavel Rappo <pavel.rappo@gmail.com>
Date
Jun 10, 2022, 12:59 UTC
Message-ID
<CAChcVumTgNqRTt=EtThXiw9ga=W9WC-uS0XOkz7T+TbtGKeU+w@mail.gmail.com>
Here's a console session:
  % git config --get-all remote.jdk19.fetch
  +refs/heads/*:refs/remotes/jdk19/*
  ^refs/heads/pr/*
  % 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

Next: Junio C Hamano
Message 1 of 6 in “Should `git remote show` display excluded branches as to-be-fetched?”
  1. Pavel RappoJun 10, 2022
  2. Junio C HamanoJun 10, 2022
  3. Jacob KellerJun 12, 2022
  4. Jacob KellerJun 13, 2022
  5. Jacob KellerJun 14, 2022
  6. Pavel RappoJun 25, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.