summaryrefslogtreecommitdiff
path: root/git-ls-remote.sh
diff options
context:
space:
mode:
authorRené Scharfe <rene.scharfe@lsrfire.ath.cx>2007-01-05 22:30:22 (GMT)
committerJunio C Hamano <junkio@cox.net>2007-01-06 18:37:14 (GMT)
commitf08b3b0e2e9ad87767d80ff03b013c686e08ba4b (patch)
treeef47c8b637e151cec1b9d68e2f24ff57ac56a9c8 /git-ls-remote.sh
parent21afc41c363cdfbc33285291d92635741163e6a1 (diff)
downloadgit-f08b3b0e2e9ad87767d80ff03b013c686e08ba4b.zip
git-f08b3b0e2e9ad87767d80ff03b013c686e08ba4b.tar.gz
git-f08b3b0e2e9ad87767d80ff03b013c686e08ba4b.tar.bz2
Set default "tar" umask to 002 and owner.group to root.root
In order to make the generated tar files more friendly to users who extract them as root using GNU tar and its implied -p option, change the default umask to 002 and change the owner name and group name to root. This ensures that a) the extracted files and directories are not world-writable and b) that they belong to user and group root. Before they would have been assigned to a user and/or group named git if it existed. This also answers the question in the removed comment: uid=0, gid=0, uname=root, gname=root is exactly what we want. Normal users who let tar apply their umask while extracting are only affected if their umask allowed the world to change their files (e.g. a umask of zero). This case is so unlikely and strange that we don't need to support it. Signed-off-by: Rene Scharfe <rene.scharfe@lsrfire.ath.cx> Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'git-ls-remote.sh')
0 files changed, 0 insertions, 0 deletions