diff options
4 files changed, 29 insertions, 1 deletions
diff --git a/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__.txt b/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__.txt index 8c62c5325..7eaf2a71b 100644 --- a/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__.txt +++ b/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__.txt @@ -31,3 +31,16 @@ local repository version: 3 default repository version: 3 supported repository versions: 3 4 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]] diff --git a/doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn b/doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn index cb295a5c4..c256778c8 100644 --- a/doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn +++ b/doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn @@ -7,3 +7,13 @@ Manually pushing the branch makes `git annex sync` sync both branches with the g I think that it should push the current branch upon creation of the special remote, since for at least me, the whole reason for wanting `git-remote-gcrypt` is that metadata as well as data can be stored encrypted on an SSH server. Thanks for considering this. + +> The git-annex branch is pushed by initremote because I have to push +> *something* to determine the gcrypt-id. However, this is an implementation +> detail, and not a feature of initremote. (It's more like a bug of +> git-remote-gcrypt.) +> +> `git annex sync` will always push your currently checked out branch, +> as well as the git-annex branch, no matter what `initremote` has done. +> +> [[done]] --[[Joey]] diff --git a/doc/git-annex.mdwn b/doc/git-annex.mdwn index b753e5462..c845e2758 100644 --- a/doc/git-annex.mdwn +++ b/doc/git-annex.mdwn @@ -552,7 +552,7 @@ subdirectories). Displays a list of repositories known to contain the contents of the specified file or files. -* `remotes` [path ...] +* `remotes [path ...]` Displays a table of remotes that contain the contents of the specified files. Unlike whereis, this only shows configured remotes, not other diff --git a/doc/todo/__96__git_annex_status__47__version__96___should_print_the_local_OS.mdwn b/doc/todo/__96__git_annex_status__47__version__96___should_print_the_local_OS.mdwn index b8b582ceb..9c2afecb4 100644 --- a/doc/todo/__96__git_annex_status__47__version__96___should_print_the_local_OS.mdwn +++ b/doc/todo/__96__git_annex_status__47__version__96___should_print_the_local_OS.mdwn @@ -1 +1,6 @@ That would make assessing weird reports like [[bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/]] easier and quicker. + +> No, if people want to file a bug report, it's up to them to tell me +> relevant details about their OS. I'm not going down the rathole +> of making git-annex muck about trying to gather such information. +> [[done]] --[[Joey]] |