From e07fbf936ac3c65a68349e44d4984e80da827f0f Mon Sep 17 00:00:00 2001
From: "https://christian.amsuess.com/chrysn" <chrysn@web>
Date: Tue, 10 Dec 2019 10:27:58 +0000
Subject: [PATCH] Added a comment: Key character set

---
 ...omment_1_4ec126bffafc81fae04e183874ffce39._comment | 11 +++++++++++
 1 file changed, 11 insertions(+)
 create mode 100644 doc/internals/key_format/comment_1_4ec126bffafc81fae04e183874ffce39._comment

diff --git a/doc/internals/key_format/comment_1_4ec126bffafc81fae04e183874ffce39._comment b/doc/internals/key_format/comment_1_4ec126bffafc81fae04e183874ffce39._comment
new file mode 100644
index 0000000000..8a3e8f7bf1
--- /dev/null
+++ b/doc/internals/key_format/comment_1_4ec126bffafc81fae04e183874ffce39._comment
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="https://christian.amsuess.com/chrysn"
+ nickname="chrysn"
+ avatar="http://christian.amsuess.com/avatar/c6c0d57d63ac88f3541522c4b21198c3c7169a665a2f2d733b4f78670322ffdc"
+ subject="Key character set"
+ date="2019-12-10T10:27:58Z"
+ content="""
+Are there limitations on the character set git-annex guarantees?
+
+It appears from experiments that git-annex only uses ASCII characters in there, given both a file 'test.extü' (in UTF-8 encoding) 'test.ext\xff' produced extension-free key names in the SHA256E hash – but it'd be good to have that confirmed.
+"""]]