On 12 April 2011 19:19, René Scharfe <rene.scharfe@xxxxxxxxxxxxxx> wrote: > The local setting of tar.umask does not affect the archive created at the > remote end. If your "remote" repository is in fact located on the same > machine and accessed with the same user then of course settings in > ~/.gitconfig will take effect. I've eventually realised this by reading the source code. The command I actually needed was: cd /repo/website.git && git -c tar.umask=0022 archive HEAD Can't comment on the proposed diff without getting better handle on the whole system, but my knee-jerk reaction would be to resist the urge to add more switches. Maybe the existing -c switch could be made to cooperate with --remote, or maybe the documentation could be edited to make it clearer that -c and --remote are not related in the way I had originally assumed. Jacek -- 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