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

Re: [PATCH v2 1/3] test: use unambigous leading path (/foo) for mingw

From
Torsten Bögershausen <tboegi@web.de>
Date
Sep 14, 2013, 06:52 UTC
Message-ID
<523407AF.9080205@web.de>
In-Reply-To
<xmqqtxhoijpz.fsf@gitster.dls.corp.google.com>
On 2013-09-13 21.51, Junio C Hamano wrote:
Show 12 quoted lines
> Jiang Xin <worldhello.net@gmail.com> writes:
> 
>> In test cases for relative_path, path with one leading character
>> (such as /a, /x) may be recogonized as "a:/" or "x:/" if there is
>> such doc drive on MINGW platform. Use an umambigous leading path
>> "/foo" instead.
> 
> "DOS drive", you mean?
> 
> Are they really spelled as /a or /x (not e.g. //a or something)?
> 
> Just double-checking.

Yes, there is a directoctory structure in / like this:

/usr /bin /lib Then we have the drive letters mapped to single letters: /c/Documents and Settings /c/temp

As an alternative c:/temp can be used or the DOS style "c:\temp"

And the // or "\\" is used for the UNC names (Universal Name Convention) //Servername/ShareName/Directory

/Torsten
Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 8 in “fixes for relative_path”
  1. 0/3 fixes for relative_pathJiang Xin, Sep 13, 2013
  2. 1/3 test: use unambigous leading path (/foo) for mingwJiang Xin, Sep 13, 2013
  3. Junio C HamanoSep 13, 2013
  4. Torsten BögershausenSep 14, 2013
  5. Junio C HamanoSep 17, 2013
  6. 2/3 relative_path should honor dos_drive_prefixJiang Xin, Sep 13, 2013
  7. Torsten BögershausenSep 14, 2013
  8. 3/3 Use simpler relative_path when set_git_dirJiang Xin, Sep 13, 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.