From: Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
To: git@vger.kernel.org
Subject: "Branch exists" error while trying to rename a non-existing branch to an existing one
Date: Sun, 09 Jul 2017 23:57:39 +0530 [thread overview]
Message-ID: <1499624859.8552.9.camel@gmail.com> (raw)
Hello all,
I recently got the following error message by change as a result of the
command,
$ git branch -m no-branch master
fatal: A branch named 'master' already exists.
Note: no-branch is an hypothetical branch that doesn't exist.
Shouldn't I get a 'no-branch' doesn't exist before that? Wouldn't this
behaviour make the users search for the non-existing 'no-branch' in
their repo?
I tried digging the implementation a little and what I could interpret
from it is,
* only the validity of new branch name (master, in the above case)
is checked
* checking for existence of the branch being renamed(no-branch) is
not done at all. It seems to be left to the lower level commands to
identify.
I'm puzzled by seeing this. Why isn't there any check for the existence
of the branch being renamed and warning the user about that first?
--
Kaartic
next reply other threads:[~2017-07-09 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 18:27 Kaartic Sivaraam [this message]
2017-07-09 18:57 ` "Branch exists" error while trying to rename a non-existing branch to an existing one Junio C Hamano
2017-07-10 14:14 ` Kaartic Sivaraam
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=1499624859.8552.9.camel@gmail.com \
--to=kaarticsivaraam91196@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).