From: mhagger@alum.mit.edu Date: Wed, 19 Oct 2011 20:55:12 GMT Subject: [RFC 09/13] new_branch(): verify that new branch name is a valid full refname Message-ID: <1319057716-28094-10-git-send-email-mhagger@alum.mit.edu> In-Reply-To: <1319057716-28094-1-git-send-email-mhagger@alum.mit.edu> From: Michael Haggerty Signed-off-by: Michael Haggerty --- Is it possible to omit the REFNAME_ALLOW_ONELEVEL option from this call? fast-import.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/fast-import.c b/fast-import.c index 8d8ea3c..51cf898 100644 --- a/fast-import.c +++ b/fast-import.c @@ -722,7 +722,7 @@ static struct branch *new_branch(const char *name) if (b) die("Invalid attempt to create duplicate branch: %s", name); - if (check_refname_format(name, REFNAME_ALLOW_ONELEVEL)) + if (check_refname_format(name, REFNAME_FULL|REFNAME_ALLOW_ONELEVEL)) die("Branch name doesn't conform to GIT standards: %s", name); b = pool_calloc(1, sizeof(struct branch)); -- 1.7.7