delta/libgit2.git/tests/path/win32.c, branch ethomson/refresh_objects github.com: libgit2/libgit2.git win32: further cleanups for 8.3 disabling 2015-02-04T01:01:24+00:00 Edward Thomson ethomson@microsoft.com 2015-02-04T01:01:24+00:00 07c989e98d013132168326eb7fd6fdf91a2399b9 






win32: cleanup 8.3 disabled tests
2015-02-03T17:23:04+00:00

Edward Thomson
ethomson@microsoft.com

2015-02-03T17:16:11+00:00

5f28ec84a10b283f79f027f83ba03d7774a987f7












Fix test failures when 8.3 is disabled
2015-01-30T16:09:31+00:00

Linquize
linquize@yahoo.com.hk

2015-01-28T15:04:50+00:00

9dcc4a36f709f013ed111924754021fddfc933e6












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.







win32: use NT-prefixed "\\?\" paths
2014-12-16T16:08:43+00:00

Edward Thomson
ethomson@microsoft.com

2014-12-01T18:09:58+00:00

cceae9a25d0bed8b00f4981e051d5f380ef54401

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:\)





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:\)