summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2013-11-15 20:39:43 +0000
committerGravatar admin <admin@branchable.com>2013-11-15 20:39:43 +0000
commitd3b9aff196729e9b95e077c65eb0e530ce1248ef (patch)
tree2599c99ccae29ce35578bcfe112a74fb2b56ad19 /doc
parentc10814d0350194f7864e2f6397771a5511966b43 (diff)
Added a comment
Diffstat (limited to 'doc')
-rw-r--r--doc/forum/_preferred_content:_lastpresent/comment_1_7610cd866b256d36646b642eb5f8cae5._comment14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/forum/_preferred_content:_lastpresent/comment_1_7610cd866b256d36646b642eb5f8cae5._comment b/doc/forum/_preferred_content:_lastpresent/comment_1_7610cd866b256d36646b642eb5f8cae5._comment
new file mode 100644
index 000000000..d5910c6d0
--- /dev/null
+++ b/doc/forum/_preferred_content:_lastpresent/comment_1_7610cd866b256d36646b642eb5f8cae5._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.246"
+ subject="comment 1"
+ date="2013-11-15T20:39:43Z"
+ content="""
+The idea seems to be to match files that have been deleted.
+
+I don't see how that could work; preferred content expressions are always matched against files in the working tree.
+
+Even if it were doable, it would be quite expensive if every preferred content query involved a `git log`...
+
+What are you trying to achieve with this?
+"""]]