diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U <Richard@web> | 2011-04-09 23:43:15 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2011-04-09 23:43:15 +0000 |
| commit | 29022a4143888bcae9b35cba427568f5da33c7da (patch) | |
| tree | c870c4fb0b88705e122273d21ec6337aed3510c9 | |
| parent | 74e877357d1f03827dc1fac438bf8ed8af0d47ad (diff) | |
| -rw-r--r-- | doc/bugs/Name_scheme_does_not_follow_git__39__s_rules.mdwn | 2 |
1 files changed, 2 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 f256b0ed1..722dac50b 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 @@ -27,3 +27,5 @@ I can create an annex remote named 'test:/test'. git itself does not allow colon >>>> Nobody spoke up to say it's unclear, so closing as PEBKAC :) >>>> [[done]] --[[Joey]] + +>>>>> I still think git-annex should follow the same rules as git in this regard, but if your design decision is different, I won't try to argue the point :) -- RichiH |