diff options
author | https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog <Michael@web> | 2014-04-17 21:19:10 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2014-04-17 21:19:10 +0000 |
commit | 13d2f3d3eff9a91beb38411fab968da42707a6f7 (patch) | |
tree | 447c963b26e9ec61ae862a06d92a93dd93e2de7a | |
parent | 57c5c5f6f74b8e0f664425cb98d88baf7ef78aa5 (diff) |
Added a comment
-rw-r--r-- | doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_2_992c1a51d0300bd676cb431688efa524._comment | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_2_992c1a51d0300bd676cb431688efa524._comment b/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_2_992c1a51d0300bd676cb431688efa524._comment new file mode 100644 index 000000000..f32a4a70f --- /dev/null +++ b/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_2_992c1a51d0300bd676cb431688efa524._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog" + nickname="Michael" + subject="comment 2" + date="2014-04-17T21:19:10Z" + content=""" +Hi Joey, + +In fact, this is indirect mode on Linux, ext4. +I'm less worried about preserving +x mode (though I can see why it would be useful). Here I'm referring to plain \"group\" and \"other\" read permissions being cleared. + +And I just did a test with a standalone rsync, using rsync -P localhost:file file2 and interrupting it, the partial (and final after resume) file2 still is 644 (and not 600 like in git-annex case). +"""]] |