From 19c5621ede14ad4b9fff39aa5b2009c0920a7c97 Mon Sep 17 00:00:00 2001 From: "https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4" Date: Mon, 15 Feb 2016 16:30:37 +0000 Subject: --- .../shouldn__39__t_keep_permissions_of_the_ssh_remote__63__.mdwn | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/bugs/shouldn__39__t_keep_permissions_of_the_ssh_remote__63__.mdwn diff --git a/doc/bugs/shouldn__39__t_keep_permissions_of_the_ssh_remote__63__.mdwn b/doc/bugs/shouldn__39__t_keep_permissions_of_the_ssh_remote__63__.mdwn new file mode 100644 index 000000000..fc9c3965e --- /dev/null +++ b/doc/bugs/shouldn__39__t_keep_permissions_of_the_ssh_remote__63__.mdwn @@ -0,0 +1,9 @@ +### Please describe the problem. + +Initially generated an annex while having a restrictive umask 077. Then cloned that repository to another host for public consumption so directory had proper/good permissions set allowing group to access. And everything is accessible but not the load which I 'annex get'ed. Key directories were readable but not the content. I guess there is somewhere 'preserve permissions' setting for rsync/scp which imho shouldn't be there and content should inherit local/environment settings + +### What version of git-annex are you using? On what operating system? + +6.20160208+gitg1ac9034-1~ndall+1 + +[[!meta author=yoh]] -- cgit v1.2.3