Am 1/11/2011 8:54, schrieb Jonathan Nieder: > Perhaps it is also worth explaining the cases where $PWD is needed? > > By contrast, when a passing a path to git or constructing a URL, > use $PWD. The first part of the "or" is not true: you can pass the result of $(pwd) to a command, and it means the same as $PWD; I would even recommend against $PWD so that a reader does not have to wonder "why pass $PWD, but check for $(pwd)?" The second part I don't know whether it is true: I haven't noticed a pattern where people did it the wrong way, therefore, I'don't even know whether $PWD is really *always* required. Do *you* know? > It makes a difference on Windows, where > > - $(pwd) is a Windows-style path such as git might output, and > - $PWD is a Unix-style path that the shell (MSYS bash) will > mangle before passing to native apps like git. This information is already included by reference to 4114156ae9. -- Hannes -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html