aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/Cannot_clone_an_annex.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-03-18 20:07:59 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-03-18 20:07:59 -0400
commitc76bcdc47e0d4a48b9b9cc91718255e89c535d05 (patch)
tree2aed28a0de95f8b8b2d0c2d440c2917b884ea2f3 /doc/bugs/Cannot_clone_an_annex.mdwn
parenta46424e78b1cd98f87ee62a49b63acff7e6d890c (diff)
bug triaging and tagging
Diffstat (limited to 'doc/bugs/Cannot_clone_an_annex.mdwn')
-rw-r--r--doc/bugs/Cannot_clone_an_annex.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/bugs/Cannot_clone_an_annex.mdwn b/doc/bugs/Cannot_clone_an_annex.mdwn
index 62e9ed27f..77989ecb6 100644
--- a/doc/bugs/Cannot_clone_an_annex.mdwn
+++ b/doc/bugs/Cannot_clone_an_annex.mdwn
@@ -65,3 +65,5 @@ the `SHA256` key is not present.
It looks like I'll have to rollback my ZFS snapshots and start over, but I'm
wondering: how was I even able to create this situation?
+
+> [[Done]]; user error. --[[Joey]]