And now, in the interests of looking a Git horse in the mouth: it's a shame about the CamelCase in the organisation and repository names. Not many people do this on GitHub; for example, GitHub's own organisation name is "github", not "GitHub", even though the company name is ordinarily written in camel case.
Stretching out before me is a grim meathook future of repeatedly typing "macruby/macruby", then seeing "ERROR: macruby/macruby.git doesn't exist", then saying GOD DAMMIT, then retyping it with the caps.
Hmm, is that really a problem? https://github.com/macruby/macruby is working as expected. I assume you would just type the camel case name once, when cloning the repository.
Case sensitivity on a file system is generally retarded. I think it was an accidental 'feature' of some file systems and now in order to be compatible everyone has to do it. Real world benefit is zero while the annoyance factor is high. Not counting lost productivity due to case related bugs....
And now, in the interests of looking a Git horse in the mouth: it's a shame about the CamelCase in the organisation and repository names. Not many people do this on GitHub; for example, GitHub's own organisation name is "github", not "GitHub", even though the company name is ordinarily written in camel case.
Stretching out before me is a grim meathook future of repeatedly typing "macruby/macruby", then seeing "ERROR: macruby/macruby.git doesn't exist", then saying GOD DAMMIT, then retyping it with the caps.