Hi list, when git-clone was built in, its treatment of umask has changed: the shell version respected umask for newly created directories by using plain mkdir(1), and the builtin version just uses mkdir(work_tree, 0755).
Is it intentional? This Stackoverflow question is what got me interested: http://stackoverflow.com/questions/10637416/git-clone-respects-umask-except-for-top-level-project-directory and might provide a credible use case. Regards, Alex -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
