From: Yaroslav Halchenko <yoh@onerussian.com>
To: Git Gurus hangout <git@vger.kernel.org>
Cc: Benjamin Poldrack <benjaminpoldrack@gmail.com>,
Michael Hanke <michael.hanke@gmail.com>
Subject: Re: wishlist; unify behavior while cloning non-bare repos over http to be in line with ssh/local
Date: Tue, 10 May 2016 15:06:52 -0400 [thread overview]
Message-ID: <20160510190652.GI7907@onerussian.com> (raw)
In-Reply-To: <20160506131855.GD7907@onerussian.com>
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
next prev parent reply other threads:[~2016-05-10 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 13:18 wishlist; unify behavior while cloning non-bare repos over http to be in line with ssh/local Yaroslav Halchenko
2016-05-10 19:06 ` Yaroslav Halchenko [this message]
2016-05-10 20:11 ` Junio C Hamano
2016-05-10 20:33 ` Jacob Keller
2016-05-10 22:10 ` Yaroslav Halchenko
2016-05-10 22:13 ` Junio C Hamano
2016-05-11 0:49 ` Yaroslav Halchenko
2016-05-11 21:27 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160510190652.GI7907@onerussian.com \
--to=yoh@onerussian.com \
--cc=benjaminpoldrack@gmail.com \
--cc=git@vger.kernel.org \
--cc=michael.hanke@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.