From: Jacob Keller <jacob.keller@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Yaroslav Halchenko <yoh@onerussian.com>,
Git Gurus hangout <git@vger.kernel.org>,
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 13:33:40 -0700 [thread overview]
Message-ID: <CA+P7+xoCmMV01=11GRVsuOSoTPgzSFT-VAeqa1SCcLnzpGcb0Q@mail.gmail.com> (raw)
In-Reply-To: <xmqqfutpoepz.fsf@gitster.mtv.corp.google.com>
On Tue, May 10, 2016 at 1:11 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Yaroslav Halchenko <yoh@onerussian.com> writes:
>
>> 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.
>
> I am afraid that the reason why you saw no response is primarily
> because nobody is interested in extending dumb commit-walker HTTP
> transport after the world has largely moved on and abandoned it.
>
> The necessary update to the client might as simple as using
> $GIVEN_URL/.git/ and attempting the request again after seeing the
> probe for $GIVEN_URL/info/refs fails.
> --
I know at least Jenkin's Git plugin has a workaround to solve this
issue that is quite similar.
Thanks,
Jake
next prev parent reply other threads:[~2016-05-10 20:34 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
2016-05-10 20:11 ` Junio C Hamano
2016-05-10 20:33 ` Jacob Keller [this message]
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='CA+P7+xoCmMV01=11GRVsuOSoTPgzSFT-VAeqa1SCcLnzpGcb0Q@mail.gmail.com' \
--to=jacob.keller@gmail.com \
--cc=benjaminpoldrack@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=michael.hanke@gmail.com \
--cc=yoh@onerussian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).