From fe202e97cb7fbd22ac9796920ea4cb0f7ef8b6ea Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 5 Jan 2015 16:58:19 -0400 Subject: comment --- ...ent_1_07a70090a9ac8f675233b08b24f55544._comment | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/forum/How_to_hide_broken_symlinks/comment_1_07a70090a9ac8f675233b08b24f55544._comment diff --git a/doc/forum/How_to_hide_broken_symlinks/comment_1_07a70090a9ac8f675233b08b24f55544._comment b/doc/forum/How_to_hide_broken_symlinks/comment_1_07a70090a9ac8f675233b08b24f55544._comment new file mode 100644 index 000000000..c4f55b85b --- /dev/null +++ b/doc/forum/How_to_hide_broken_symlinks/comment_1_07a70090a9ac8f675233b08b24f55544._comment @@ -0,0 +1,22 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-01-05T20:52:11Z" + content=""" +This works, but it's very inneficient. You're +adding metadata (which is committed to git!) to represent location information. +git-annex already knows about location information, +so it could just look at it and use it to build the view. + +The reason I haven't implemented this yet is I'm not clear about what to do +if a file is dropped while in a view. It seems like git-annex should update +the view to no longer show the dropped file. But this means that any change +to a file's presence needs to update the view, and so it entangles the +implementation of views with a core part of git-annex. And it might be +pretty inneficient to need to build a new view branch each time a file is +dropped too. + +With your hack, the view doesn't automatically update when a file is +dropped. Since you're using it this way, maybe you have some advice or +thoughts about this question? +"""]] -- cgit v1.2.3