From: Denys Dmytriyenko <denis@denix.org>
To: Ryan D Phillips <ryan_d_phillips@dell.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: Introduction and Request for HTTP Git Access
Date: Tue, 09 Nov 2010 13:06:58 -0500 [thread overview]
Message-ID: <20101109180658.GB8761@denix.org> (raw)
In-Reply-To: <4CD98638.8050306@dell.com>
On Tue, Nov 09, 2010 at 11:34:48AM -0600, Ryan D Phillips wrote:
> On 11/9/2010 11:22 AM, Darren Hart wrote:
>> On 11/09/2010 09:02 AM, Denys Dmytriyenko wrote:
>>> On Tue, Nov 09, 2010 at 10:31:37AM -0600, Ryan_D_Phillips@Dell.com wrote:
>>>> Good Day!
>>>>
>>>> My name is Ryan Phillips (irc: rphillips), a former Gentoo Linux
>>>> Developer,
>>>> currently a software developer architecting an embedded firmware
>>>> solution on
>>>> OE for my employer. With the release of Yocto, we are extremely
>>>> interested
>>>> in trying it out and possibly contributing to the project. My cohort
>>>> working
>>>> with me is Sean Hudson (irc: darknighte), and is someone who you may see
>>>> contributions from as well.
>>>>
>>>> A major stumbling block we must work around is the restrictive firewall
>>>> and
>>>> git checkouts. We have found out the git-http-backend works extremely
>>>> well,
>>>> and are requesting this support on git.pokylinux.org. We suspect other
>>>> people within larger corporations would have a similar problem, and by
>>>> adding this support would help the community at large.
>>>
>>> Ryan,
>>>
>>> It's nice to see another Gentooist!
>>>
>>> Have you looked at core.gitProxy setting or GIT_PROXY_COMMAND environment
>>> in
>>> git-config(1)? People behind strict firewalls been using that for years
>>> to
>>> tunnel their git access through proxies. Used together with things like
>>> netcat, socat or corkscrew work miracles even with HTTP-only proxies!
>>
>> It is certainly sub-ideal (but so is git over http), but it should
>> provide the functionality you need. Please give the above a shot and if
>> for some reason it is insufficient, please let us know.
>>
>
> I don't understand the comment that git over http is sub-ideal (see github
> using https for git by default), but the issue we have is the proxy server
> restricts outbound ports to 80 and 443, and doesn't allow CONNECT.
git-over-http used to be sub-ideal until version 1.6.6 of git, as it only
provided "dumb" read-only access. Now, with git-http-backend(1) there is a
"smart" transport available, which can also handle pushing over https...
http://www.kernel.org/pub/software/scm/git/docs/git-http-backend.html
http://progit.org/2010/03/04/smart-http.html
--
Denys
next prev parent reply other threads:[~2010-11-09 18:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 16:31 Introduction and Request for HTTP Git Access Ryan_D_Phillips
2010-11-09 17:02 ` Denys Dmytriyenko
2010-11-09 17:22 ` Darren Hart
2010-11-09 17:34 ` Ryan D Phillips
2010-11-09 18:06 ` Denys Dmytriyenko [this message]
2010-11-09 18:35 ` Darren Hart
2010-11-09 18:05 ` Scott Garman
2010-11-09 18:31 ` Denys Dmytriyenko
2010-11-09 21:46 ` Ryan D Phillips
2010-11-10 0:10 ` Richard Purdie
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=20101109180658.GB8761@denix.org \
--to=denis@denix.org \
--cc=poky@yoctoproject.org \
--cc=ryan_d_phillips@dell.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