git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Pavel Rappo <pavel.rappo@gmail.com>
To: git@vger.kernel.org
Subject: Should `git remote show` display excluded branches as to-be-fetched?
Date: Fri, 10 Jun 2022 13:59:03 +0100	[thread overview]
Message-ID: <CAChcVumTgNqRTt=EtThXiw9ga=W9WC-uS0XOkz7T+TbtGKeU+w@mail.gmail.com> (raw)

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

             reply	other threads:[~2022-06-10 12:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 12:59 Pavel Rappo [this message]
2022-06-10 17:08 ` Should `git remote show` display excluded branches as to-be-fetched? Junio C Hamano
2022-06-12  6:36   ` Jacob Keller
2022-06-13 23:20   ` Jacob Keller
2022-06-14  0:34     ` Jacob Keller
2022-06-25 16:06       ` Pavel Rappo

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAChcVumTgNqRTt=EtThXiw9ga=W9WC-uS0XOkz7T+TbtGKeU+w@mail.gmail.com' \
    --to=pavel.rappo@gmail.com \
    --cc=git@vger.kernel.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).