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	-5/+3
\|
*	win32: cleanup 8.3 disabled tests	Edward Thomson	2015-02-03	1	-16/+7
\|
*	Fix test failures when 8.3 is disabled	Linquize	2015-01-31	1	-3/+17
\|
*	checkout: disallow bad paths on win32	Edward Thomson	2014-12-16	1	-0/+24
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	win32: use NT-prefixed "\\?\" paths	Edward Thomson	2014-12-16	1	-0/+190
	When turning UTF-8 paths into UCS-2 paths for Windows, always use the \\?\-prefixed paths. Because this bypasses the system's path canonicalization, handle the canonicalization functions ourselves. We must: 1. always use a backslash as a directory separator 2. only use a single backslash between directories 3. not rely on the system to translate "." and ".." in paths 4. remove trailing backslashes, except at the drive root (C:\)