Poky Project Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@linux.intel.com>
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: Wed, 10 Nov 2010 08:10:28 +0800	[thread overview]
Message-ID: <1289347828.1272.78.camel@rex> (raw)
In-Reply-To: <4CD9C14F.7010902@dell.com>

On Tue, 2010-11-09 at 15:46 -0600, Ryan D Phillips wrote:
> On 11/9/2010 12:31 PM, Denys Dmytriyenko wrote:
> > On Tue, Nov 09, 2010 at 10:05:29AM -0800, Scott Garman wrote:
> >> On 11/09/2010 08:31 AM, 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.
> >>>
> >
> 
> Hmm. I didn't mean to start a firestorm. Read only git-http-backend 
> access is something that we would find useful. As an alternative, we can 
> create repo.or.cz mirrors, but I'm not all that keen on this.

I'm travelling at the moment so I'll just keep this brief.

I'm more than happy to try and find a way to share git.yoctoproject.org
over http for cloning, that shouldn't be too hard. I'll see if I can get
something working next week although I'm meant to be taking some
vacation too.

For push access over https, that is a lot more difficult as it is
unlikely to integrate well with our access control system. I'd need to
do more reading before I could really comment on that. It appears
changes in git support it better at least.

Cheers,

Richard



      reply	other threads:[~2010-11-10  0:36 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
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 [this message]

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=1289347828.1272.78.camel@rex \
    --to=rpurdie@linux.intel.com \
    --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