delta/libgit2.git - github.com: libgit2/libgit2.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	win32: further cleanups for 8.3 disabling	Edward Thomson	2015-02-03	1	-4/+1
\|
*	win32: cleanup 8.3 disabled tests	Edward Thomson	2015-02-03	1	-23/+7
\|
*	Fix test failures when 8.3 is disabled	Linquize	2015-01-31	1	-1/+23
\|
*	checkout tests: nasty symlinks	Edward Thomson	2015-01-20	1	-1/+39
\| \| \| \|	Symbolic links that abuse case insensitivity to write into .git.
*	Introduce core.protectHFS and core.protectNTFS	Edward Thomson	2014-12-17	1	-0/+32
\| \| \| \| \| \|	Validate HFS ignored char ".git" paths when `core.protectHFS` is specified. Validate NTFS invalid ".git" paths when `core.protectNTFS` is specified.
*	checkout: disallow bad paths on HFS	Edward Thomson	2014-12-16	1	-0/+42
\| \| \| \| \| \| \| \|	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	Edward Thomson	2014-12-16	1	-0/+251
	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.