From 6adc0d2b3fcfc01a3d95fb2b7400315736a6cec1 Mon Sep 17 00:00:00 2001
From: Joey Hess <joeyh@joeyh.name>
Date: Mon, 27 Aug 2018 15:10:05 -0400
Subject: [PATCH] bug triage

---
 doc/todo/smudge.mdwn | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/doc/todo/smudge.mdwn b/doc/todo/smudge.mdwn
index 81263a4ed1..af144b543b 100644
--- a/doc/todo/smudge.mdwn
+++ b/doc/todo/smudge.mdwn
@@ -25,8 +25,21 @@ git-annex should use smudge/clean filters. v6 mode
   (My enhanced smudge/clean patch set also fixed this problem, in a much
   nicer way...)
 
+* <http://git-annex.branchable.com/bugs/inAnnex_check_failed_repeatedly_for_present_content_v6/>
+
+  I have this mostly analized and need to implement the planned fix.
+
 ## other warts
 
+* There are several v6 bugs that are edge cases and
+  need more info or analysis. None of these seem like blockers
+  to keep v6 experimental or to replacing direct mode with v6.
+
+  - <http://git-annex.branchable.com/bugs/assistant_crashes_in_TransferScanner/>
+  - <http://git-annex.branchable.com/bugs/v6_appears_to_not_thin/>
+  - <http://git-annex.branchable.com/bugs/Metadata_views_in_v6_repo_upgraded_from_direct_mode_act_strangely/>a
+  - <http://git-annex.branchable.com/bugs/git-annex-sync_sometimes_fails_in_submodule_in_V6_adjusted_branch/>
+
 * When git runs the smudge filter, it buffers all its output in ram before
   writing it to a file. So, checking out a branch with a large v6 unlocked files
   can cause git to use a lot of memory.