aboutsummaryrefslogtreecommitdiff
path: root/doc/todo
diff options
context:
space:
mode:
authorGravatar zardoz <zardoz@web>2014-05-13 20:34:33 +0000
committerGravatar admin <admin@branchable.com>2014-05-13 20:34:33 +0000
commit8644c73b75666fd1a7d7c80b538997a10b9c82dd (patch)
tree8aca3fdb5cb244531af58215937d46733ad08d7e /doc/todo
parent60d27d0c59e1899026ba447ec4ff8579e25e20f0 (diff)
Added a comment
Diffstat (limited to 'doc/todo')
-rw-r--r--doc/todo/Enhancement:_git_annex_whereis_KEY/comment_1_5d768ab0065e6ecbc8ea25d66c226758._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/todo/Enhancement:_git_annex_whereis_KEY/comment_1_5d768ab0065e6ecbc8ea25d66c226758._comment b/doc/todo/Enhancement:_git_annex_whereis_KEY/comment_1_5d768ab0065e6ecbc8ea25d66c226758._comment
new file mode 100644
index 000000000..eb60a25d3
--- /dev/null
+++ b/doc/todo/Enhancement:_git_annex_whereis_KEY/comment_1_5d768ab0065e6ecbc8ea25d66c226758._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="zardoz"
+ ip="92.227.51.179"
+ subject="comment 1"
+ date="2014-05-13T20:34:33Z"
+ content="""
+I suppose that makes sense. Is it more affordable to just retrieve the most recent filename? That would seem to be enough for many practical purposes. But I guess this would still possibly have to go through many revisions. I wonder if such a restricted search can be done by git though. Maybe using non-porcelain commands.
+"""]]