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

close

Browse source
This commit is contained in:
Joey Hess 2013-09-12 12:40:23 -04:00
parent e3c7b505cd
commit 39f99411eb
1 changed files with 13 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

13
doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__.txt
View file

@ -31,3 +31,16 @@ local repository version: 3
default repository version: 3 default repository version: 3
supported repository versions: 3 4 supported repository versions: 3 4
upgrade supported from repository versions: 0 1 2 upgrade supported from repository versions: 0 1 2
> git-annex intentionally treats UUIDs as opaque strings,
> so it is not going to go to any bother to consider
> different byte sequences to be the same UUID, sorry.
> (The standard may be arbitrarily complicated, but I have arbitrarily
> decided to ignore it.)
>
> Since git-annex only ever generates each UUID once, and copies
> the exact sequence of bytes as necessary, the only way the situation
> you show above can happen is if you have manually gone in and entered
> UUIDs in two different cases.
>
> [[done]] --[[Joey]]