summaryrefslogtreecommitdiff
path: root/doc/backends/comment_4_46591a3ba888fb686b1b319b80ca2c22._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/backends/comment_4_46591a3ba888fb686b1b319b80ca2c22._comment')
-rw-r--r--doc/backends/comment_4_46591a3ba888fb686b1b319b80ca2c22._comment9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/backends/comment_4_46591a3ba888fb686b1b319b80ca2c22._comment b/doc/backends/comment_4_46591a3ba888fb686b1b319b80ca2c22._comment
new file mode 100644
index 000000000..94f25e996
--- /dev/null
+++ b/doc/backends/comment_4_46591a3ba888fb686b1b319b80ca2c22._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawmTho3mActvetF1iQdmui6gH1t6WE6c284"
+ nickname="Michael"
+ subject="SHA256e"
+ date="2013-10-30T02:00:45Z"
+ content="""
+I'd really like to have a SHA256e backend -- same as SHA256E but making sure that extensions of the files in .git/annex are converted to lower case. I normally try to convert filenames from cameras etc to lower case, but not all people that I share annex with do so consistently.
+In my use case, I need to be able to find duplicates among files and .jpg vs .JPG throws git annex dedup off. Otherwise E backends are superior to non-E for me. Thanks, Michael.
+"""]]