Bug 3263

Summary: Enable read-only HTTP access to repos at git.yoctoproject.org
Product: [Infrastructure] Website Reporter: Evadeflow <evadeflow>
Component: web-contentAssignee: Michael Halstead <mhalstead>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium CC: Infras.watcher, infras.web.watcher, sgw
Version: unspecified   
Target Milestone: Future   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Evadeflow 2012-10-09 16:35:13 UTC 
As discussed during the technical team meeting today, it is difficult for
people behind a strict corporate firewall to track mainline development of the
various repos under the Yocto Project umbrella because they all use 'git://'
protocol, which is usually blocked. Having read-only HTTP access would allow
developers behind a firewall who are working on a stable branch to also track
master, and thus submit patches for any bugs they find against master instead
of whatever branch they're on.

Git-over-HTTP used to be much less efficient, but I guess that has changed:

  - http://git-scm.com/2010/03/04/smart-http.html


Nowadays (mostly thanks to github), it's common (and kind of 'expected') for
projects to offer access via both git:// and http://...
Comment 1 Michael Halstead 2012-10-18 20:03:00 UTC 
Read-only HTTP/HTTPS access to repos at git.yoctoproject.org is ready.

URLs are listed at the bottom of cgit project pages after the clone
heading. Visit http://git.yoctoproject.org/cgit/cgit.cgi/poky/ for an
example. They follow the pattern
http://git.yoctoproject.org/git/[repo_path].

Git can be configured to use an http proxy by setting the http_proxy
environment variable or by running 'git config http.proxy [proxy_url]'.