From 48b471e1df2b0f6ad0b2d350228257c96cbdc9e3 Mon Sep 17 00:00:00 2001 From: cehteh Date: Wed, 26 Mar 2014 20:03:51 +0000 Subject: [PATCH] Added a comment --- ..._517c7659654a6fc608eb3332053df8a4._comment | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 doc/forum/view_from_numeric_values/comment_4_517c7659654a6fc608eb3332053df8a4._comment diff --git a/doc/forum/view_from_numeric_values/comment_4_517c7659654a6fc608eb3332053df8a4._comment b/doc/forum/view_from_numeric_values/comment_4_517c7659654a6fc608eb3332053df8a4._comment new file mode 100644 index 0000000000..90cb1c22a9 --- /dev/null +++ b/doc/forum/view_from_numeric_values/comment_4_517c7659654a6fc608eb3332053df8a4._comment @@ -0,0 +1,28 @@ +[[!comment format=mdwn + username="cehteh" + ip="217.8.62.137" + subject="comment 4" + date="2014-03-26T20:03:51Z" + content=""" +I agree with you that things must stay simple. All what should be done is having the same effects like normal globs but adding arithmetic comparisons to it (could you think about a globbing extension over numeric values?). Then the generated views will have the same properties/semnatic as the normal glob'ed views without other side effects (if you want to go that far, this would even hold true for disjunct, parenthesized and otherwise complex expression). + +Example (how it should work, except my bug report 'set metadata on wrong files') + + git annex metadata a.txt -s foo=bar -s num=1 + git annex metadata b.txt -s foo=baz -s num=2 + git annex metadata c.txt -s foo=barf -s num=3 + + git annex view foo=bar* num=* -ne 2 + +should give + ./bar/1/a.txt ./barf/3/c.txt + +am I right now than one could + + mkdir -p ./baz/2 + mv /bar/1/a.txt ./baz/2 + +to change the metadata of a.txt, despite the foo=baz and num=2 fields where initially filtered out when creating the view? +If this assumption is true then having arithmetic filters, no matter how complex they are won't change the existing semantics over what globs do. + +"""]]