summaryrefslogtreecommitdiff
path: root/doc/bugs/git_annex_gets_confused_about_remotes_with_dots_in_their_names.mdwn
blob: 6f35cef8d1d855ba22fdb12ba50dbd159706ebc1 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
For test.com//test, I get this:

    % git annex copy . --to test.com//test
    (getting UUID for test...) git-annex: there is no git remote named "test.com//test"

And my .git/config changes from

    [remote "test.com//test"]
    	url = richih@test.com:/test
    	fetch = +refs/heads/*:refs/remotes/test.com//test/*

to

    [remote "test.com//test"]
    	url = richih@test.com:/test
    	fetch = +refs/heads/*:refs/remotes/test.com//test/*
    	annex-uuid = xyz
    [remote "test"]
    	annex-uuid = xyz


Unless I am misunderstanding something, git annex gets confused about what the name of the remote it supposed to be, truncates at the dot for some operations and uses the full name for others.

> I've fixed this bug. [[done]]
> 
> However, using "/" in a remote name seems likely to me to confuse 
> git's own remote branch handling. Although I've never tried it.
> --[[Joey]]