4 Commits

Author	SHA1	Message	Date
Carlos Martín Nieto	e5ef0f1814	refs: handle ALLOW_ONELEVEL normalization with leading slash ... A leading slash confuses the name normalization code when the flags include ALLOW_ONELEVEL. Catch this case in particular to avoid triggering an assertion in the uppercase check which expects us not to pass it an empty string. The existing tests don't catch this as they simply use the NORMAL flag. This fixes #1300.	2013-01-31 20:23:30 +01:00
nulltoken	2df37f42c1	refs: cover more refname validity edge cases	2012-10-18 23:59:22 +02:00
nulltoken	5912d74c69	revparse: properly handle refnames containing a @ ... Fix #994	2012-10-18 23:05:33 +02:00
nulltoken	77e06d7e85	refs: introduce git_reference_is_valid_name()	2012-09-25 07:49:15 +02:00