From: "ClementMabileau via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: ClementMabileau <mabileau.clement@gmail.com>
Subject: [PATCH 0/2] branch: improve error log on branch not found by checking remotes refs
Date: Wed, 22 Mar 2023 09:42:04 +0000 [thread overview]
Message-ID: <pull.1476.git.git.1679478126.gitgitgadget@gmail.com> (raw)
when failing to delete a branch with git branch -d <branch> because of
branch not found, try to find a remote refs matching <branch> and if so add
an hint: Did you forget --remote? to the error message
ctmbl (2):
branch: improve error log on branch not found by checking remotes refs
Fix mem leak in branch.c due to not-free newly added virtual_name
variable
builtin/branch.c | 29 ++++++++++++++++++++++++-----
1 file changed, 24 insertions(+), 5 deletions(-)
base-commit: 950264636c68591989456e3ba0a5442f93152c1a
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1476%2Fctmbl%2Fbranch%2Fdeletion%2Fimprove-error-msg-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1476/ctmbl/branch/deletion/improve-error-msg-v1
Pull-Request: https://github.com/git/git/pull/1476
--
gitgitgadget
next reply other threads:[~2023-03-22 9:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 9:42 ClementMabileau via GitGitGadget [this message]
2023-03-22 9:42 ` [PATCH 1/2] branch: improve error log on branch not found by checking remotes refs ctmbl via GitGitGadget
2023-03-22 9:42 ` [PATCH 2/2] Fix mem leak in branch.c due to not-free newly added virtual_name variable ctmbl via GitGitGadget
2023-03-22 16:52 ` Junio C Hamano
2023-03-22 20:00 ` Clement Mabileau
2023-03-22 20:52 ` Junio C Hamano
2023-03-22 20:03 ` [PATCH v2] branch: improve error log on branch not found by checking remotes refs ClementMabileau via GitGitGadget
2023-03-22 22:25 ` Junio C Hamano
2023-03-23 15:51 ` Clement Mabileau
2023-04-04 13:30 ` Clement Mabileau
2023-04-04 16:24 ` Junio C Hamano
2023-04-05 9:15 ` Clement Mabileau
2023-04-05 11:43 ` [PATCH v3] " ClementMabileau via GitGitGadget
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=pull.1476.git.git.1679478126.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=mabileau.clement@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.
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).