RE: DNS entry for git.haskell.org active now!
Thanks. Some quick questions 1. What's the difference between ghc.haskell.org and git.haskell.org? 2. Is there anything to choose between these two? ./sync-all -r git://git.haskell.org remote set-url origin ./sync-all -rhttp://git.haskell.org remote set-url origin 3. The repositories page http://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/Repositories says this page has been replaced by Repositories but the link is circular.. leads to the same page. 4. The Gitolite plan page http://ghc.haskell.org/trac/ghc/wiki/GitolitePlan is very helpful, but is in the nature of a delta/change-over plan. Are you planning to replace it (perhaps on Repositories?) with instructions for how to use the new setup? I think that would be v helpful for dolts like me. Simon | -Original Message- | From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of | Herbert Valerio Riedel | Sent: 19 August 2013 23:46 | To: ghc-devs | Subject: DNS entry for git.haskell.org active now! | | Hello GHC Devs, | | Hopefully, the new DNS entry for git.haskell.org should be visible for | all of you by the time you read this. This mostly completes the | migration part of the GitolitePlan[1]. | | With the new hostname, the URLs to use for `sync-all` to fetch via | git://, http://, or ssh:// (ordered by increasing latency url length) | are | | ./sync-all -r git://git.haskell.org remote set-url origin | ./sync-all -rhttp://git.haskell.org remote set-url origin | ./sync-all -r ssh://g...@git.haskell.org remote set-url origin | | ...and for setting the push-URL (via ssh://) use | | ./sync-all -r ssh://g...@git.haskell.org remote set-url --push origin | | Please note that the (deprecated) `/libraries` symlink to `/packages` is | only supported at the old http://darcs.haskell.org/ Git repo location. | | Finally, the new Gitweb interface[2] to the GHC Git repos should have | become accessible for everyone (w/o hacking `/etc/hosts`). | | Cheers, | hvr | | [1]: http://ghc.haskell.org/trac/ghc/wiki/GitolitePlan | [2]: http://git.haskell.org/ | | ___ | ghc-devs mailing list | ghc-devs@haskell.org | http://www.haskell.org/mailman/listinfo/ghc-devs ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
RE: DNS entry for git.haskell.org active now!
| However, in order to facilitate future migrations, git.haskell.org | should be used, as then we could relocate git.haskell.org to a different | IP without needing to update the URLs in all documents again. Why? If we only had ghc.haskell.org, we could just migrate that couldn't we? Or are you imagining a situation in which ghc.haskell.org and git.haskell.org were really different servers? Trac on one, and the repo on another, say? Hmm. maybe that makes sense. It'd be good to explain this thinking on the wiki page that you are developing. | Does this answer your question? :-) Yes, v helpful. Please copy paste the answer into the new wiki page! | 3. The repositories page | http://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/Repositories | says this page has been replaced by Repositories but the link is | circular.. leads to the same page. You didn't reply to this. Thanks S ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
Re: DNS entry for git.haskell.org active now!
On 2013-08-20 at 09:48:48 +0200, Simon Peyton-Jones wrote: | However, in order to facilitate future migrations, git.haskell.org | should be used, as then we could relocate git.haskell.org to a different | IP without needing to update the URLs in all documents again. Why? If we only had ghc.haskell.org, we could just migrate that couldn't we? Or are you imagining a situation in which ghc.haskell.org and git.haskell.org were really different servers? Trac on one, and the repo on another, say? Hmm. maybe that makes sense. Here's some more motivation why a new git.haskell.org hostname was desired: http://permalink.gmane.org/gmane.comp.lang.haskell.infrastructure/103 It'd be good to explain this thinking on the wiki page that you are developing. will do | Does this answer your question? :-) Yes, v helpful. Please copy paste the answer into the new wiki page! will do | 3. The repositories page | http://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/Repositories | says this page has been replaced by Repositories but the link is | circular.. leads to the same page. You didn't reply to this. I've fixed this right now; seems the semantics changed for wiki: links in Trac 0.12, so that wiki:Repositories was a link relative to /WorkingConventions/ instead of pointing to /Repositories. Cheers, hvr ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
DNS entry for git.haskell.org active now!
Hello GHC Devs, Hopefully, the new DNS entry for git.haskell.org should be visible for all of you by the time you read this. This mostly completes the migration part of the GitolitePlan[1]. With the new hostname, the URLs to use for `sync-all` to fetch via git://, http://, or ssh:// (ordered by increasing latency url length) are ./sync-all -r git://git.haskell.org remote set-url origin ./sync-all -rhttp://git.haskell.org remote set-url origin ./sync-all -r ssh://g...@git.haskell.org remote set-url origin ...and for setting the push-URL (via ssh://) use ./sync-all -r ssh://g...@git.haskell.org remote set-url --push origin Please note that the (deprecated) `/libraries` symlink to `/packages` is only supported at the old http://darcs.haskell.org/ Git repo location. Finally, the new Gitweb interface[2] to the GHC Git repos should have become accessible for everyone (w/o hacking `/etc/hosts`). Cheers, hvr [1]: http://ghc.haskell.org/trac/ghc/wiki/GitolitePlan [2]: http://git.haskell.org/ ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
Re: DNS entry for git.haskell.org active now!
Thank you Herbert! On Monday, August 19, 2013, Herbert Valerio Riedel wrote: Hello GHC Devs, Hopefully, the new DNS entry for git.haskell.org should be visible for all of you by the time you read this. This mostly completes the migration part of the GitolitePlan[1]. With the new hostname, the URLs to use for `sync-all` to fetch via git://, http://, or ssh:// (ordered by increasing latency url length) are ./sync-all -r git://git.haskell.org remote set-url origin ./sync-all -rhttp://git.haskell.org remote set-url origin ./sync-all -r ssh://g...@git.haskell.org javascript:; remote set-url origin ...and for setting the push-URL (via ssh://) use ./sync-all -r ssh://g...@git.haskell.org javascript:; remote set-url --push origin Please note that the (deprecated) `/libraries` symlink to `/packages` is only supported at the old http://darcs.haskell.org/ Git repo location. Finally, the new Gitweb interface[2] to the GHC Git repos should have become accessible for everyone (w/o hacking `/etc/hosts`). Cheers, hvr [1]: http://ghc.haskell.org/trac/ghc/wiki/GitolitePlan [2]: http://git.haskell.org/ -- Sent from my portable turning machine ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
