summaryrefslogtreecommitdiff
path: root/doc/bugs/git_annex_gets_confused_about_remotes_with_dots_in_their_names.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/git_annex_gets_confused_about_remotes_with_dots_in_their_names.mdwn')
-rw-r--r--doc/bugs/git_annex_gets_confused_about_remotes_with_dots_in_their_names.mdwn6
1 files changed, 6 insertions, 0 deletions
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 e6dee3e0b..6f35cef8d 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
@@ -20,3 +20,9 @@ to
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]]