mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Added a comment: Non-E backend drawbacks?

Browse source
This commit is contained in:
https://www.google.com/accounts/o8/id?id=AItOawmWBvsZvSsAL8P2ye3F0OBStjFCVnOImzM 2013-10-30 21:25:04 +00:00 committed by admin
parent 8df88ea448
commit fcdc917e22
1 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/backends/comment_5_2210c7ff2d5812fb3b778ac172291656._comment Normal file
View file

@ -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?
"""]]