summaryrefslogtreecommitdiff
path: root/doc/backends/comment_5_2210c7ff2d5812fb3b778ac172291656._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/backends/comment_5_2210c7ff2d5812fb3b778ac172291656._comment')
-rw-r--r--doc/backends/comment_5_2210c7ff2d5812fb3b778ac172291656._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/backends/comment_5_2210c7ff2d5812fb3b778ac172291656._comment b/doc/backends/comment_5_2210c7ff2d5812fb3b778ac172291656._comment
new file mode 100644
index 000000000..2a205604c
--- /dev/null
+++ b/doc/backends/comment_5_2210c7ff2d5812fb3b778ac172291656._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawmWBvsZvSsAL8P2ye3F0OBStjFCVnOImzM"
+ nickname="Jarno"
+ subject="Non-E backend drawbacks?"
+ date="2013-10-30T21:25:00Z"
+ content="""
+The page states \"[non-E backends] can confuse some programs\". I like the ideal simplicity and recoverability of pure checksum backends but \"confusion\" sounds a bit worrying. Any practical examples of these problems to help me choose?
+"""]]