| 
| Git vs Http protocol [message #1357] | Sat, 04 April 2009 15:14  |  | 
| Eclipse User  |  |  |  |  | Originally posted by: alex_blewitt.yahoo.com 
 I tried to download EGit with "git clone git://repo.or.cz/egit.git" but
 firewall problems appear to be blocking the git port (9418?). Apparently,
 git can work over HTTP as well (which was one of the selling points over
 SVN for authenticated access) but when I tried to do "  git clone
 http://repo.or.cz/egit.git" I got a 'Cannot get remote repository
 information' message. Is that because the 'repo.or.cz' server hasn't been
 set up to provide the Git repo over HTTP as well?
 
 Alex
 |  |  |  | 
|  | 
|  | 
| 
| Re: Git vs Http protocol [message #1415 is a reply to message #1405] | Tue, 07 April 2009 14:19  |  | 
| Eclipse User  |  |  |  |  | Alex Blewitt wrote: > OK, thanks. In general, other VCS use the same path regardless of
 > protocol (c.f. CVS's pserver vs ssh). It would be good if, when setting
 > up git.eclipse.org, we could ensure that we have the same path for both
 > git:: and http:: access. Given that the git.eclipse.org will probably be
 > a vserver on the back end, and we can probably reserve the full path
 > name for just git repository access, I hope that it's not going to be a
 > problem.
 
 Yea, I agree.
 
 repo.or.cz is a quirk; its a dedicated hosting site that pretty much
 *only* runs git repositories for open source projects, and yet it is
 configured to use different paths for git://, ssh:// and http://.
 
 Its possible to use the same path for everything, and any
 git.eclipse.org server should certainly do that.
 |  |  |  | 
| 
| Re: Git vs Http protocol [message #570386 is a reply to message #1357] | Sun, 05 April 2009 00:20  |  | 
| Eclipse User  |  |  |  |  | Alex Blewitt wrote: 
 > I tried to download EGit with "git clone git://repo.or.cz/egit.git" but
 > firewall problems appear to be blocking the git port (9418?). Apparently,
 > git can work over HTTP as well (which was one of the selling points over
 > SVN for authenticated access) but when I tried to do "  git clone
 > http://repo.or.cz/egit.git" I got a 'Cannot get remote repository
 > information' message. Is that because the 'repo.or.cz' server hasn't been
 > set up to provide the Git repo over HTTP as well?
 
 No, you were using the wrong URL. I updated the page with the http option.
 In general, a project's gitweb page, when available, will show all the
 URL's for different protocols.
 
 -- robin
 |  |  |  | 
| 
| Re: Git vs Http protocol [message #570571 is a reply to message #1374] | Tue, 07 April 2009 03:51  |  | 
| Eclipse User  |  |  |  |  | OK, thanks. In general, other VCS use the same path regardless of protocol (c.f. CVS's pserver vs ssh). It would be good if, when setting up
 git.eclipse.org, we could ensure that we have the same path for both git::
 and http:: access. Given that the git.eclipse.org will probably be a
 vserver on the back end, and we can probably reserve the full path name
 for just git repository access, I hope that it's not going to be a problem.
 
 Alex
 |  |  |  | 
| 
| Re: Git vs Http protocol [message #570626 is a reply to message #1405] | Tue, 07 April 2009 14:19  |  | 
| Eclipse User  |  |  |  |  | Alex Blewitt wrote: > OK, thanks. In general, other VCS use the same path regardless of
 > protocol (c.f. CVS's pserver vs ssh). It would be good if, when setting
 > up git.eclipse.org, we could ensure that we have the same path for both
 > git:: and http:: access. Given that the git.eclipse.org will probably be
 > a vserver on the back end, and we can probably reserve the full path
 > name for just git repository access, I hope that it's not going to be a
 > problem.
 
 Yea, I agree.
 
 repo.or.cz is a quirk; its a dedicated hosting site that pretty much
 *only* runs git repositories for open source projects, and yet it is
 configured to use different paths for git://, ssh:// and http://.
 
 Its possible to use the same path for everything, and any
 git.eclipse.org server should certainly do that.
 |  |  |  | 
Powered by 
FUDForum. Page generated in 0.03637 seconds