branch: split validate_new_branchname() into two
Checking if a proposed name is appropriate for a branch is strictly a subset of checking if we want to allow creating or updating a branch with such a name. The mysterious sounding 'attr_only' parameter to validate_new_branchname() is used to switch the function between these two roles. Instead, split the function into two, and adjust the callers. A new helper validate_branchname() only checks the name and reports if the branch already exists. This loses one NEEDSWORK from the branch API. Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
@ -463,7 +463,6 @@ static void copy_or_rename_branch(const char *oldname, const char *newname, int
|
||||
struct strbuf oldref = STRBUF_INIT, newref = STRBUF_INIT, logmsg = STRBUF_INIT;
|
||||
struct strbuf oldsection = STRBUF_INIT, newsection = STRBUF_INIT;
|
||||
int recovery = 0;
|
||||
int clobber_head_ok;
|
||||
|
||||
if (!oldname) {
|
||||
if (copy)
|
||||
@ -487,9 +486,10 @@ static void copy_or_rename_branch(const char *oldname, const char *newname, int
|
||||
* A command like "git branch -M currentbranch currentbranch" cannot
|
||||
* cause the worktree to become inconsistent with HEAD, so allow it.
|
||||
*/
|
||||
clobber_head_ok = !strcmp(oldname, newname);
|
||||
|
||||
validate_new_branchname(newname, &newref, force, clobber_head_ok);
|
||||
if (!strcmp(oldname, newname))
|
||||
validate_branchname(newname, &newref);
|
||||
else
|
||||
validate_new_branchname(newname, &newref, force);
|
||||
|
||||
reject_rebase_or_bisect_branch(oldref.buf);
|
||||
|
||||
|
Reference in New Issue
Block a user