summaryrefslogtreecommitdiff
path: root/Python/future.c
diff options
context:
space:
mode:
authorNeal Norwitz <nnorwitz@gmail.com>2005-10-20 04:50:13 +0000
committerNeal Norwitz <nnorwitz@gmail.com>2005-10-20 04:50:13 +0000
commitb0e32e2b71633211be6a62d1afaa250fb23cd3b4 (patch)
tree8c15e8edb03fba3a429fff0c5be609e6439bf745 /Python/future.c
parent40563eddf17f072a74eba0bf7b77229f77bcc3d3 (diff)
downloadcpython-git-b0e32e2b71633211be6a62d1afaa250fb23cd3b4.tar.gz
Fix SF bug # 1330039, patch # 1331635 from Lars Gustaebel (tarfile maintainer)
Problem: if two files are assigned the same inode number by the filesystem, the second one will be added as a hardlink to the first, which means that the content will be lost. The patched code checks if the file's st_nlink is greater 1. So only for files that actually have several links pointing to them hardlinks will be created, which is what GNU tar does. Will backport.
Diffstat (limited to 'Python/future.c')
0 files changed, 0 insertions, 0 deletions