retitle; known bug

doc/bugs/Unchanged_files_are_detected_as_modified_in_unlocked_branch.mdwn

@@ -19,3 +19,5 @@ The only way to rectify this I can find is `git checkout` - but that means I hav
 ### What version of git-annex are you using? On what operating system?
 
 git-annex version: 6.20171026-gd451d333d (standalone binary) on Debian stretch.
+
+[[!meta title="v6 get/drop make git think files are changed"]]

doc/bugs/Unchanged_files_are_detected_as_modified_in_unlocked_branch/comment_1_d5e90cf5edf189bb023deb46b5ffe96c._comment

@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2017-11-09T15:56:41Z"
+ content="""
+This is one of the primary known problems with v6 mode. On the page
+[[todo/smudge]] that collects all such issues, it's the second item.
+Basically, when git-annex gets/drops the content of the file, it
+updates the work tree file, and so git thinks the file has changed.
+Currently the best way to deal with it is to run `git add` on the file.
+"""]]

stack.yaml

@@ -21,6 +21,7 @@ extra-deps:
 - bloomfilter-2.0.1.0
 - torrent-10000.1.1
 - yesod-default-1.2.0
+- optparse-applicative-0.14.0.0
 explicit-setup-deps:
   git-annex: true
 resolver: lts-9.9