D Herring <dherring@xxxxxxxxxxxx> writes: > One problem: Even though the working directory is g+swx and git was > initialized with --shared=group or --shared=0660, the checked out > source files still don't have group write permissions... It is working as designed. "shared" setting is about a shared central repository that is typically a bare repository, and currently it is implemented as such. You could argue that the behaviour for the work tree files is undefined and make the code act differently, though. In any case, it would be better to document this, and it might even make sense to issue a warning message when we detect the repository is used with a work tree (including the use of GIT_DIR and GIT_WORK_TREE environment variables to temporarily turn a bare repository with a work tree). Thanks for a report. -- 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