From: "Kiril Ivanov via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Kiril Ivanov <ivanovkirilg@gmail.com>
Subject: [PATCH 0/3] git-prompt: add quiet upstream indicator option
Date: Sat, 15 Nov 2025 18:54:20 +0000 [thread overview]
Message-ID: <pull.2101.git.git.1763232863.gitgitgadget@gmail.com> (raw)
This patch series allows a cleaner git-prompt when the upstream indicator is
not actionable.
In particular, the '=' to the upstream can be redundant noise if the user is
always on a remote-tracking branch and only needs to be aware of any
divergence.
Since SHOWUPSTREAM already supports various options, I propose a new 'quiet'
option to limit it to actionable output (omit '=')
* Default: branch =
* Verbose: branch|u=
* Verbose name: branch|u= remote/branch
* Quiet: branch
* Verbose quiet: branch|u
* Verbose quiet name: branch|u remote/branch
Ahead/behind output is unaffected (default <> or verbose +N-M).
Kiril Ivanov (3):
t9903: shorten setup using test_commit
t9903: add upstream indicator tests
git-prompt: add quiet upstream indicator option
contrib/completion/git-prompt.sh | 14 ++++--
t/t9903-bash-prompt.sh | 86 ++++++++++++++++++++++++++------
2 files changed, 80 insertions(+), 20 deletions(-)
base-commit: fd372d9b1a69a01a676398882bbe3840bf51fe72
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2101%2Fivanovkirilg%2Fquiet-option-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2101/ivanovkirilg/quiet-option-v1
Pull-Request: https://github.com/git/git/pull/2101
--
gitgitgadget
next reply other threads:[~2025-11-15 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-15 18:54 Kiril Ivanov via GitGitGadget [this message]
2025-11-15 18:54 ` [PATCH 1/3] t9903: shorten setup using test_commit Kiril Ivanov via GitGitGadget
2025-11-15 18:54 ` [PATCH 2/3] t9903: add upstream indicator tests Kiril Ivanov via GitGitGadget
2025-11-15 18:54 ` [PATCH 3/3] git-prompt: add quiet upstream indicator option Kiril Ivanov via GitGitGadget
2025-11-20 16:01 ` D. Ben Knoble
2025-11-20 18:05 ` Eric Sunshine
2025-11-20 18:18 ` D. Ben Knoble
2025-11-15 20:07 ` [PATCH 0/3] " Junio C Hamano
2025-11-16 12:05 ` Kiril Ivanov
2025-11-16 16:55 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.2101.git.git.1763232863.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=ivanovkirilg@gmail.com \
/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.
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 NNTP newsgroup(s).