summaryrefslogtreecommitdiff
path: root/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_1_00b52dba3bc30516e06c44cbfd3a05a2._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_1_00b52dba3bc30516e06c44cbfd3a05a2._comment')
-rw-r--r--doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_1_00b52dba3bc30516e06c44cbfd3a05a2._comment17
1 files changed, 0 insertions, 17 deletions
diff --git a/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_1_00b52dba3bc30516e06c44cbfd3a05a2._comment b/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_1_00b52dba3bc30516e06c44cbfd3a05a2._comment
deleted file mode 100644
index b1417816f..000000000
--- a/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_1_00b52dba3bc30516e06c44cbfd3a05a2._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2013-09-12T09:44:54Z"
- content="""
-There does not seem to be an actual bug description in here. Can you provide more info?
-
-To answer the actual question: RFC 4122 clearly answers no:
-
- Each field is treated as an integer and has its value printed as a
- zero-filled hexadecimal digit string with the most significant
- digit first. The hexadecimal values \"a\" through \"f\" are output as
- lower case characters and are case insensitive on input.
-
-Yes, that means that git-annex prints them wrongly as that's upper case.
-"""]]