diff options
author | 2011-03-19 01:16:09 +0000 | |
---|---|---|
committer | 2011-03-19 01:16:09 +0000 | |
commit | 9e8d5373365281f67b9539e0443572e92bde5b60 (patch) | |
tree | 0d5c96257f6d7f25b5151d34b9e7439b324ccbe5 | |
parent | debc7b27445da764561abd83044e7865024b39f0 (diff) |
-rw-r--r-- | doc/bugs/Name_scheme_does_not_follow_git__39__s_rules.mdwn | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/bugs/Name_scheme_does_not_follow_git__39__s_rules.mdwn b/doc/bugs/Name_scheme_does_not_follow_git__39__s_rules.mdwn index aa658819b..597188889 100644 --- a/doc/bugs/Name_scheme_does_not_follow_git__39__s_rules.mdwn +++ b/doc/bugs/Name_scheme_does_not_follow_git__39__s_rules.mdwn @@ -4,3 +4,17 @@ I can create an annex remote named 'test:/test'. git itself does not allow colon > remotes configuration as does git. If you put invalid > stuff in .git/config it might handle it slightly different than > git, I don't know. Examples needed. --[[Joey]] + +>> What I mean is this: + + % cd 1 + % git init + % git annex init "my:colon" + % [...] + % cd ../2 + % git init + % git annex init "second" + % git remote add "my:colon" ../1 + fatal: 'my:colon' is not a valid remote name + +>> -- RichiH |