diff options
author | Joey Hess <joey@kitenet.net> | 2011-03-18 16:29:14 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2011-03-18 16:29:14 -0400 |
commit | 0cc05e0c19d7e0a6112167440a9ba48629407625 (patch) | |
tree | da847e33dceedb1d54affb56a9c0201aa68ba1fa | |
parent | efd555848d042450d867761799ebd1b23459ea4e (diff) |
response
-rw-r--r-- | doc/bugs/Name_scheme_does_not_follow_git__39__s_rules.mdwn | 5 |
1 files changed, 5 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 8399ff984..aa658819b 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 @@ -1 +1,6 @@ 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]] |