From e144b45dd5335d119f31e3253edef94acabee3b9 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 31 May 2013 21:17:17 +0000 Subject: [PATCH] Added a comment --- ...comment_1_fc8d3ea209a2ab39c1aeff52452d4c58._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/assistant_doesn__39__t_sync_file_permissions/comment_1_fc8d3ea209a2ab39c1aeff52452d4c58._comment diff --git a/doc/bugs/assistant_doesn__39__t_sync_file_permissions/comment_1_fc8d3ea209a2ab39c1aeff52452d4c58._comment b/doc/bugs/assistant_doesn__39__t_sync_file_permissions/comment_1_fc8d3ea209a2ab39c1aeff52452d4c58._comment new file mode 100644 index 0000000000..9e1b801a4e --- /dev/null +++ b/doc/bugs/assistant_doesn__39__t_sync_file_permissions/comment_1_fc8d3ea209a2ab39c1aeff52452d4c58._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 1" + date="2013-05-31T21:17:17Z" + content=""" +More generally, symbolic links cannot have permissions of their own, and git in fact indicates a file is a symlink by setting the tree object's mode to a specific magic number. So there is no git metadata that git-annex can use to track whether a file is supposed to be executable. + +Therefore, this will only get fixed when there's some kind of full-fledged metadata storage for git. +"""]]