From: "Josh Hunt via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Josh Hunt <joshua.hunt@berkeley.edu>, Josh Hunt <johunt@akamai.com>
Subject: [PATCH] branch: return error when --list finds no matches
Date: Wed, 03 Mar 2021 17:44:51 +0000 [thread overview]
Message-ID: <pull.892.git.1614793491538.gitgitgadget@gmail.com> (raw)
From: Josh Hunt <johunt@akamai.com>
Currently git branch --list foo always returns an exit status of 0 even
when the branch being searched for does not exist. Now an error is printed
and returns a non-zero exit status.
Signed-off-by: Josh Hunt <johunt@akamai.com>
---
branch: return error when --list finds no matches
Currently git branch --list foo always returns an exit status of 0 even
when the branch being searched for does not exist. Now an error is
printed and returns a non-zero exit status.
Signed-off-by: Josh Hunt johunt@akamai.com
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-892%2Fjoshuahunt%2Fjohunt%2Fgit-branch-list-return-error-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-892/joshuahunt/johunt/git-branch-list-return-error-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/892
builtin/branch.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/builtin/branch.c b/builtin/branch.c
index bcc00bcf182d..5573175734fe 100644
--- a/builtin/branch.c
+++ b/builtin/branch.c
@@ -426,6 +426,8 @@ static void print_ref_list(struct ref_filter *filter, struct ref_sorting *sortin
memset(&array, 0, sizeof(array));
filter_refs(&array, filter, filter->kind | FILTER_REFS_INCLUDE_BROKEN);
+ if (!array.nr)
+ die(_("no branches found"));
if (filter->verbose)
maxwidth = calc_maxwidth(&array, strlen(remote_prefix));
base-commit: ec125d1bc1053df7e4103f71ebd24fe48dd624a2
--
gitgitgadget
next reply other threads:[~2021-03-04 0:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 17:44 Josh Hunt via GitGitGadget [this message]
2021-03-04 1:27 ` [PATCH] branch: return error when --list finds no matches Junio C Hamano
2021-03-05 0:46 ` Josh Hunt
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.892.git.1614793491538.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=johunt@akamai.com \
--cc=joshua.hunt@berkeley.edu \
/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).