From d55deb61091688ea02c1cd0ebb153e626826ed34 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 17 Feb 2015 17:51:29 -0400 Subject: comment --- .../comment_2_7dbfa3da6ae72a1f0669396664dd0c1a._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/forum/optimising_lookupkey/comment_2_7dbfa3da6ae72a1f0669396664dd0c1a._comment diff --git a/doc/forum/optimising_lookupkey/comment_2_7dbfa3da6ae72a1f0669396664dd0c1a._comment b/doc/forum/optimising_lookupkey/comment_2_7dbfa3da6ae72a1f0669396664dd0c1a._comment new file mode 100644 index 000000000..8b3c973d4 --- /dev/null +++ b/doc/forum/optimising_lookupkey/comment_2_7dbfa3da6ae72a1f0669396664dd0c1a._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2015-02-17T21:50:11Z" + content=""" +And yes, it's fine to bypass git-annex when querying git. + +Or even when manipulating the git-annex branch, so long as you either +delete or update .git/annex/index. git-annex is not intended to be magical, +see [[internals]]. +"""]] -- cgit v1.2.3