diff options
| author |  Michael Haggerty <mhagger@alum.mit.edu> | 2011-08-25 21:19:24 +0200 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2011-08-25 13:39:38 -0700 |
| commit | 2f633f41d69527cdd9ff5b8e04a752f1774fc3df (patch) | |
| tree | 54f2510c9df67e803e5f2f49cdbc3a9071160218 /t/t3900-i18n-commit.sh | |
| parent | completion: replace core.abbrevguard to core.abbrev (diff) | |
| download | tgif-2f633f41d69527cdd9ff5b8e04a752f1774fc3df.tar.xz | |
check-ref-format --print: Normalize refnames that start with slashes
When asked if "refs///heads/master" is valid, check-ref-format says "Yes,
it is well formed", and when asked to print canonical form, it shows
"refs/heads/master". This is so that it can be tucked after "$GIT_DIR/"
to form a valid pathname for a loose ref, and we normalize a pathname like
"$GIT_DIR/refs///heads/master" to de-dup the slashes in it.
Similarly, when asked if "/refs/heads/master" is valid, check-ref-format
says "Yes, it is Ok", but the leading slash is not removed when printing,
leading to "$GIT_DIR//refs/heads/master".
Fix it to make sure such leading slashes are removed. Add tests that such
refnames are accepted and normalized correctly.
Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t3900-i18n-commit.sh')
0 files changed, 0 insertions, 0 deletions