From: John Tapsell <johnflux@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: [PATCH 3/6] Improve error message for branching an existing branch
Date: Thu, 19 Feb 2009 07:36:24 +0000 [thread overview]
Message-ID: <200902190736.24402.johnflux@gmail.com> (raw)
Signed-off-by: John Tapsell <johnflux@gmail.com>
---
branch.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/branch.c b/branch.c
index 1f00e44..86ac293 100644
--- a/branch.c
+++ b/branch.c
@@ -120,7 +120,8 @@ void create_branch(const char *head,
if (resolve_ref(ref.buf, sha1, 1, NULL)) {
if (!force)
- die("A branch named '%s' already exists.", name);
+ die("A branch named '%s' already exists.\n"
+ "Maybe you wanted to change to this branch with: git checkout '%s'", name, name);
else if (!is_bare_repository() && !strcmp(head, name))
die("Cannot force update the current branch.");
forcing = 1;
--
1.6.2.rc1.3.g7d31b.dirty
reply other threads:[~2009-02-19 7:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200902190736.24402.johnflux@gmail.com \
--to=johnflux@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.
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).