On Fri, 06 May 2016, Yaroslav Halchenko wrote: > Dear Git Folks,
> Originally this issue was mentioned in previous thread [1], and I have decided > to bring it into a separate thread. ATM there is a dichotomy in git behavior > between cloning non-bare repos: if I clone over ssh or just locally by > providing url without trailing /.git, git senses for /.git and works just fine > with ssh or local repositories, but fails for "dummy" http ones, the demo > script is here [2] which produces output listed below. From which you can see > that cloning using http URL to the repository without /.git fails (git > version > 2.8.1, Debian). As it was noted in [1], concern could have been to not > traverse website since could lead to dangerous places. But .git is under > originating url directory, as well as info/ or HEAD or any other object > accessed by git, so IMHO this concern is not a concern. > ... If there is a better venue (bug tracker?) to spark the interest and discussion, please let me know ;) -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
