aboutsummaryrefslogtreecommitdiff
path: root/sha1_name.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2017-10-13 13:45:40 +0900
committerJunio C Hamano <gitster@pobox.com>2017-10-13 17:11:41 +0900
commitbc1c9c0e674bdd293c29ae84365915848ed01d7a (patch)
treeddde1bceda59ec50837294f152d49834aa9d6bdd /sha1_name.c
parent8280c4c1ea59bc6d101c5616490627b63934318e (diff)
downloadgit-bc1c9c0e674bdd293c29ae84365915848ed01d7a.tar.gz
git-bc1c9c0e674bdd293c29ae84365915848ed01d7a.tar.xz
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>
Diffstat (limited to 'sha1_name.c')
0 files changed, 0 insertions, 0 deletions