[Current] URL git://git.overlays.gentoo.org/proj/sunrise-reviewed.git http://git.overlays.gentoo.org/gitroot/proj/sunrise-reviewed.git git+ssh://git@git.overlays.gentoo.org/proj/sunrise-reviewed.git [Wanted] URL git://git.overlays.gentoo.org/proj/sunrise-reviewed.git http://git.overlays.gentoo.org/gitroot/proj/sunrise-reviewed.git https://git.overlays.gentoo.org/gitroot/proj/sunrise-reviewed.git git+ssh://git@git.overlays.gentoo.org/proj/sunrise-reviewed.git Thanks!
Done
Any thoughts on removing http:// ?? 4 URLs is getting abit excessive for people not so familar with git. (IMO)
I would prefer not to show http and https at all tbh, the git daemon and git+ssh are the preferred ones either way. Sebastian/Christian, opinions please
http(s) is for people behind a proxy/firewall. We should add https links as well but we should try to add a note that http(s) should be only used for the mentioned cases.
Definitely need to keep http*, can't rely soley on git & git+ssh
Ok, so here is a solution: - Remove http and keep https only in gitweb - Add somewhere in our overlays docs that http/https should be used for people behind proxy/firewall How about this?
https may be restricted as well, in some cases.
I know, I am just proposing a solution in order to have 3 URL's listed in gitweb instead of 4. If you believe that all four of them should stay in gitweb, I will point out somewhere in the overlays docs that http(s) should be used as backup, and we can close this bug again.
Since the issue is NOT important, and we spend way more time discussing it than we should, I removed http from gitweb and I'll mention about all the clone URL choices in an overlays doc
(In reply to comment #2) > Any thoughts on removing http:// ?? 4 URLs is getting abit excessive for > people not so familar with git. (IMO) How about this space-saving approach: git://git.overlays.gentoo.org/proj/genkernel.git http://... or https://git.overlays.gentoo.org/gitroot/proj/genkernel.git git+ssh://git@git.overlays.gentoo.org/proj/genkernel.git Too ugly? (In reply to comment #7) > https may be restricted as well, in some cases. That makes a good reason to keep http listed in my eyes. (In reply to comment #9) > Since the issue is NOT important, and we spend way more time discussing it > than we should, I removed http from gitweb and I'll mention about all the > clone URL choices in an overlays doc No reason rush. I'm happy that HTTPS is in there now.
