From 3dbff3356d14eadc3463693ae44921b98d7e03f4 Mon Sep 17 00:00:00 2001
From: 
 "https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
 <Richard@web>
Date: Sat, 19 Mar 2011 01:09:22 +0000
Subject:

---
 ..._annex_gets_confused_about_remotes_with_dots_in_their_names.mdwn | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/bugs/git_annex_gets_confused_about_remotes_with_dots_in_their_names.mdwn b/doc/bugs/git_annex_gets_confused_about_remotes_with_dots_in_their_names.mdwn
index 6f35cef8d..d35282e75 100644
--- a/doc/bugs/git_annex_gets_confused_about_remotes_with_dots_in_their_names.mdwn
+++ b/doc/bugs/git_annex_gets_confused_about_remotes_with_dots_in_their_names.mdwn
@@ -26,3 +26,9 @@ Unless I am misunderstanding something, git annex gets confused about what the n
 > 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]] 
+
+>> From what I can see, git handles / just fine, but would get upset about : which is why it's not allowed in a remote's name.
+>> My naming scheme is host//path/to/annex. It sorts nicely and gives all important information left to right with the most specific parts at the beginning and end.
+>> If you have any other ideas or scheme, I am all ears :)
+>> Either way, thanks for fixing this so quickly.
+>> -- RichiH
-- 
cgit v1.2.3