Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > Hi, > > On Thu, 2 Jan 2014, Sebastian Schuberth wrote: > >> See https://github.com/msysgit/git/pull/80. > > Thanks Sebastian! > > However, since the git.git project is not comfortable with the concept of > pull requests (which is why you submitted this patch via mail), I believe > that we have to explain the rationale in the commit message. So here goes > my attempt: Thanks; the conclusion is correct --- you need a good commit message in the recorded history. That does not have anything to do with integrating with pulling from subsystem maintainers, which we regularly do. > On Linux, we can get away with assuming that the directory separator is a > forward slash, but that is wrong in general. For that purpose, the > is_dir_sep() function was introduced a long time ago. By using it in > safe_create_leading_directories(), we proof said function for use on > platforms where the directory separator is different from Linux'. Perhaps with s|Linux|POSIX|, but more importantly, was there a specific error scenario that triggered this change? My quick reading of "git grep" suggests that the callsites of this function all assume that they are to use slashes as directory separators, and it may be that it is a bug in the specific caller that throws a backslash-separated paths to it. -- 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