summaryrefslogtreecommitdiff
path: root/doc/bugs/Name_scheme_does_not_follow_git__39__s_rules.mdwn
blob: 597188889151b14ac11d377e01979b691011bd7d (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
I can create an annex remote named 'test:/test'. git itself does not allow colons in names, though. The name scheme for an annex should be the same as for git repos themselves.

> What do you mean by "an annex remote"? git-annex uses the same
> 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