summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar anarcat <anarcat@web>2016-02-01 19:54:39 +0000
committerGravatar admin <admin@branchable.com>2016-02-01 19:54:39 +0000
commitc793d53ad7588ba28202756b66a724ab4bdf52a9 (patch)
tree82e01f0ee0cfe6196cfa5ef4ca7226d070ad1e2a
parent674dc62d0865f8e403ba425ac2091e849b98c02e (diff)
-rw-r--r--doc/todo/hide_missing_files.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/todo/hide_missing_files.mdwn b/doc/todo/hide_missing_files.mdwn
index fb6984954..4f7b4b561 100644
--- a/doc/todo/hide_missing_files.mdwn
+++ b/doc/todo/hide_missing_files.mdwn
@@ -4,4 +4,6 @@ Now this behavior has changed, and with v6 coming up, all those distinctions hav
So what's someone to do if he wants to deal with the usability issue mentioned above? To restate: the problem is users I share files with often see a *lot* of files, with only a fraction of them being actually present. A lot of those files are obviously large, and so they are having a frustrating experience with git-annex because they see all those promises of "files being there" but they have a hard time actually finding which files *really* are there. So they click one one broken link after the other and generally give up before they figure out how to pop a terminal open, use `find -L -type l` or `find -type l` (i can never remember which!) - something we can hardly expect from the average GUI user...
+Maybe this could be accomplished through a [[dumb, unsafe, human-readable backend]]?
+
Thanks for any advice! --[[anarcat]]