summaryrefslogtreecommitdiff
path: root/userdiff.c
diff options
context:
space:
mode:
authorMatthew Rogers <mattr94@gmail.com>2019-11-17 23:16:10 (GMT)
committerJunio C Hamano <gitster@pobox.com>2019-11-18 03:49:17 (GMT)
commitcd5522271f6b985114b33332e148bff2283b0440 (patch)
tree82824b8da5b4d71776b43c8755f939c4a7f85b40 /userdiff.c
parent867bc1d236b8955414b3dbacf28c7f0c2e337cf4 (diff)
downloadgit-cd5522271f6b985114b33332e148bff2283b0440.zip
git-cd5522271f6b985114b33332e148bff2283b0440.tar.gz
git-cd5522271f6b985114b33332e148bff2283b0440.tar.bz2
rebase -r: let `label` generate safer labels
The `label` todo command in interactive rebases creates temporary refs in the `refs/rewritten/` namespace. These refs are stored as loose refs, i.e. as files in `.git/refs/rewritten/`, therefore they have to conform with file name limitations on the current filesystem in addition to the accepted ref format. This poses a problem in particular on NTFS/FAT, where e.g. the colon, double-quote and pipe characters are disallowed as part of a file name. Let's safeguard against this by replacing not only white-space characters by dashes, but all non-alpha-numeric ones. However, we exempt non-ASCII UTF-8 characters from that, as it should be quite possible to reflect branch names such as `↯↯↯` in refs/file names. Signed-off-by: Matthew Rogers <mattr94@gmail.com> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'userdiff.c')
0 files changed, 0 insertions, 0 deletions