tag option_to_explain dandi
authorJoey Hess <joeyh@joeyh.name>
Tue, 25 Jul 2023 15:08:33 +0000 (11:08 -0400)
committerJoey Hess <joeyh@joeyh.name>
Tue, 25 Jul 2023 15:08:33 +0000 (11:08 -0400)
See comment, this is a continuation of the other todo that was tagged
dandi and which I didn't fully address at the time.

doc/todo/a_way_to_figure_out_the_origin_of_largefiles/comment_3_def75a3ad8907cb62eb5d96c85aabd5e._comment [new file with mode: 0644]
doc/todo/option_to_explain.mdwn

diff --git a/doc/todo/a_way_to_figure_out_the_origin_of_largefiles/comment_3_def75a3ad8907cb62eb5d96c85aabd5e._comment b/doc/todo/a_way_to_figure_out_the_origin_of_largefiles/comment_3_def75a3ad8907cb62eb5d96c85aabd5e._comment
new file mode 100644 (file)
index 0000000..c1e1165
--- /dev/null
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2023-07-25T15:04:28Z"
+ content="""
+Hmm, --show-origin only implements part of what was requested here. The
+other part is to explain what part of a largefiles expression caused it to
+match (or not match).
+
+I think that nobodyinperson's suggestion of --explain got into my brain
+and marinated a while, because I later opened [[todo/option_to_explain]].
+"""]]
index cc92fc6d190f21376e086756cd4309f47220ac4b..1a504a2f15ca29f01ecbe5b313e5136993c62ea0 100644 (file)
@@ -36,3 +36,5 @@ doesn't match?" And a term like "standard" would ideally expand out the
 included expression, eg: "standard(group==backup, include==*)" 
 
 [[!tag confirmed]] --[[Joey]]
+
+[[!tag projects/dandi]]