git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/2] relative_path should honor dos_drive_prefix

From
Karsten Blees <karsten.blees@gmail.com>
Date
Sep 12, 2013, 15:45 UTC
Message-ID
<5231E1AD.6090206@gmail.com>
In-Reply-To
<0688d5a5bd194ff5808c555e8e75132e2c687368.1378977052.git.worldhello.net@gmail.com>
Am 12.09.2013 11:12, schrieb Jiang Xin:
Show 10 quoted lines
> Tvangeste found that the "relative_path" function could not work
> properly on Windows if "in" and "prefix" have dos driver prefix.
> ($gmane/234434)
> 
> e.g., When execute: test-path-utils relative_path "C:/a/b" "D:/x/y",
> should return "C:/a/b", but returns "../../C:/a/b", which is wrong.
> 
> So make relative_path honor dos_drive_prefix, and add test cases
> for it in t0060.
> 
I still don't think that cd'ing through the root is a Good Thing for absolute paths, as it is not possible to do so in general.
POSIX says the meaning of '//' is implementation-defined [1].
Cygwin supports //hostname/share/directory/file. You cannot cd to the hostname (i.e. root would be //hostname/share).

On Windows, we have drive letters, UNC paths and namespaces: C:\directory\file \\hostname\share\directory\file (same as cygwin) \\?\C:\directory\file \\?\UNC\hostname\share\directory\file

I'm not sure about '//' support on other git platforms (the most likely candidate would probably be HP-UX, as HP bought Apollo/DomainOS, which supported '//hostname/directory/file back in 1981).
You could of course handle all these special cases. However, with the POSIX definition above, the only reliable and future-proof way to check if we can cd out of a path component of an _absolute_ path is to actually try it until we get an error. And we probably don't want to do actual IO in relative_path (which is pure string manipulation so far).
[1] http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xbd_chap04.html#tag_21_04_12
Previous: Torsten BögershausenNext: Torsten Bögershausen
Message 47 of 48 in “Regression in e02ca72: git svn rebase is broken on Windows”
  1. TvangesteSep 10, 2013
  2. Johannes SchindelinSep 10, 2013
  3. TvangesteSep 10, 2013
  4. Johannes SchindelinSep 10, 2013
  5. TvangesteSep 10, 2013
  6. Johannes SixtSep 10, 2013
  7. TvangesteSep 10, 2013
  8. Junio C HamanoSep 10, 2013
  9. Karsten BleesSep 10, 2013
  10. Jiang XinSep 11, 2013
  11. Jiang XinSep 11, 2013
  12. Johannes SixtSep 11, 2013
  13. 1/2 relative_path should honor dos_drive_prefixJiang Xin, Sep 12, 2013
  14. 2/2 Use simpler relative_path when set_git_dirJiang Xin, Sep 12, 2013
  15. Johannes SixtSep 12, 2013
  16. TvangesteSep 12, 2013
  17. Torsten BögershausenSep 12, 2013
  18. Junio C HamanoSep 12, 2013
  19. Johannes SixtSep 12, 2013
  20. Junio C HamanoSep 12, 2013
  21. Jiang XinSep 13, 2013
  22. Junio C HamanoSep 13, 2013
  23. Jiang XinSep 17, 2013
  24. 1/3 test: use unambigous leading path (/foo) for mingwJiang Xin, Sep 17, 2013
  25. 2/3 relative_path should honor DOS and UNC pathsJiang Xin, Sep 17, 2013
  26. Junio C HamanoSep 17, 2013
  27. Jiang XinSep 18, 2013
  28. Junio C HamanoSep 18, 2013
  29. 3/3 Use simpler relative_path when set_git_dirJiang Xin, Sep 17, 2013
  30. Johannes SixtSep 17, 2013
  31. Torsten BögershausenSep 18, 2013
  32. Jiang XinSep 20, 2013
  33. 0/3 relative path regression fixJiang Xin, Sep 20, 2013
  34. 1/3 test: use unambigous leading path (/foo) for mingwJiang Xin, Sep 20, 2013
  35. Sebastian SchuberthOct 10, 2013
  36. Jiang XinOct 14, 2013
  37. 0/3 relative path regression fixJiang Xin, Oct 14, 2013
  38. 1/3 test: use unambigous leading path (/foo) for MSYSJiang Xin, Oct 14, 2013
  39. Sebastian SchuberthOct 14, 2013
  40. Eric SunshineOct 14, 2013
  41. 2/3 relative_path should honor dos-drive-prefixJiang Xin, Oct 14, 2013
  42. 3/3 Use simpler relative_path when set_git_dirJiang Xin, Oct 14, 2013
  43. 2/3 relative_path should honor dos-driver-prefixJiang Xin, Sep 20, 2013
  44. Sebastian SchuberthOct 10, 2013
  45. 3/3 Use simpler relative_path when set_git_dirJiang Xin, Sep 20, 2013
  46. Torsten BögershausenSep 13, 2013
  47. Karsten BleesSep 12, 2013
  48. Torsten BögershausenSep 18, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.