From 7a03f55aa0197cecf4656ccdbe87bb08d3d2af77 Mon Sep 17 00:00:00 2001 From: "https://openid.stackexchange.com/user/27ceb3c5-0762-42b8-8f8a-ed21c284748f" <g@web> Date: Thu, 10 Dec 2015 03:45:09 +0000 Subject: [PATCH] Added a comment: The downside --- ...ment_4_35d0472cd64335eedeeb17d51cdbaf5b._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/devblog/day_339_smudging_out_direct_mode/comment_4_35d0472cd64335eedeeb17d51cdbaf5b._comment diff --git a/doc/devblog/day_339_smudging_out_direct_mode/comment_4_35d0472cd64335eedeeb17d51cdbaf5b._comment b/doc/devblog/day_339_smudging_out_direct_mode/comment_4_35d0472cd64335eedeeb17d51cdbaf5b._comment new file mode 100644 index 0000000000..6690bd93ba --- /dev/null +++ b/doc/devblog/day_339_smudging_out_direct_mode/comment_4_35d0472cd64335eedeeb17d51cdbaf5b._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="https://openid.stackexchange.com/user/27ceb3c5-0762-42b8-8f8a-ed21c284748f" + nickname="g" + subject="The downside" + date="2015-12-10T03:45:09Z" + content=""" +If I'm understanding correctly, that one downside (requiring all checkouts to have all files be direct if any filesystems require it) seems to be a fairly major limitation, no? Changing the concept of locked/unlocked files from being a local, per-repo concern to a global one seems like quite a major change. + +For instance, would mean that any public repo using git annex for distributing a set of data files would either have to have all files be unlocked, or else no one would be able clone onto a FAT32-formatted external hdd? + + +FWIW, the particular use case I'm concerned about personally is having my annexes on my android device. +"""]]