delta/libgit2.git/tests/resources/nasty, branch cmn/https-cap-no-hardcode github.com: libgit2/libgit2.git checkout tests: nasty symlinks 2015-01-20T23:13:09+00:00 Edward Thomson ethomson@edwardthomson.com 2015-01-14T18:15:34+00:00 232bc89598947823e57431df63a5d6d41ad218c3 Symbolic links that abuse case insensitivity to write into .git. 
Symbolic links that abuse case insensitivity to write into .git.
checkout: disallow bad paths on HFS 2014-12-16T16:08:59+00:00 Edward Thomson ethomson@microsoft.com 2014-12-11T00:12:16+00:00 11d67b754d47967642570f796601e8850f001d73 HFS filesystems ignore some characters like U+200C. When these characters are included in a path, they will be ignored for the purposes of comparison with other paths. Thus, if you have a ".git" folder, a folder of ".git<U+200C>" will also match. Protect our ".git" folder by ensuring that ".git<U+200C>" and friends do not match it. 
HFS filesystems ignore some characters like U+200C.  When these
characters are included in a path, they will be ignored for the
purposes of comparison with other paths.  Thus, if you have a ".git"
folder, a folder of ".git<U+200C>" will also match.  Protect our
".git" folder by ensuring that ".git<U+200C>" and friends do not match it.
checkout: disallow bad paths on win32 2014-12-16T16:08:53+00:00 Edward Thomson ethomson@microsoft.com 2014-11-25T23:13:00+00:00 a64119e3963fcd358ba914c9e1a81a890666d15a Disallow: 1. paths with trailing dot 2. paths with trailing space 3. paths with trailing colon 4. paths that are 8.3 short names of .git folders ("GIT~1") 5. paths that are reserved path names (COM1, LPT1, etc). 6. paths with reserved DOS characters (colons, asterisks, etc) These paths would (without \\?\ syntax) be elided to other paths - for example, ".git." would be written as ".git". As a result, writing these paths literally (using \\?\ syntax) makes them hard to operate with from the shell, Windows Explorer or other tools. Disallow these. 
Disallow:
 1. paths with trailing dot
 2. paths with trailing space
 3. paths with trailing colon
 4. paths that are 8.3 short names of .git folders ("GIT~1")
 5. paths that are reserved path names (COM1, LPT1, etc).
 6. paths with reserved DOS characters (colons, asterisks, etc)

These paths would (without \\?\ syntax) be elided to other paths - for
example, ".git." would be written as ".git".  As a result, writing these
paths literally (using \\?\ syntax) makes them hard to operate with from
the shell, Windows Explorer or other tools.  Disallow these.