Re: Mailing list reorganisation
Sounds good, even if one wants to receive everything it's much easier to robustly filter the incoming mail when it comes from different addresses. Niklas 2012/12/11 Ian Lynagh i...@well-typed.com: Hi all, Following a recent discussion, we propose to reorganise the GHC-related mailing lists so that we end up with: glasgow-haskell-users For user discussions ghc-devs For developer discussions ghc-commits For automated commit messages from the git repositories ghc-builds For automated nightly build reports ghc-tickets For automated messages from trac We would remove cvs-ghc cvs-libraries cvs-other glasgow-haskell-bugs but leave the archives in place, and for now forwarding messages to cvs-* to ghc-devs, and glasgow-haskell-bugs to ghc-tickets. (cvs-libraries and cvs-other are included in this list, because we think they are mainly used by libraries that GHC HQ maintains, or by GHC's lagging repos of libraries that other people maintain). The initial subscriber lists for ghc-devs, ghc-commits and ghc-builds would be the union of the subscribers of cvs-ghc, cvs-libraries and cvs-other. For ghc-tickets it would be the subscriber list for glasgow-haskell-bugs. Does that sound reasonable? Does anyone have any further questions or comments? Thanks Ian ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: Mailing list reorganisation
indeed! when can we anticipate this rollout! also: props to all for such a rapid concensus on this topic! :) -carter On Wed, Dec 12, 2012 at 11:11 AM, Niklas Larsson metanik...@gmail.comwrote: Sounds good, even if one wants to receive everything it's much easier to robustly filter the incoming mail when it comes from different addresses. Niklas 2012/12/11 Ian Lynagh i...@well-typed.com: Hi all, Following a recent discussion, we propose to reorganise the GHC-related mailing lists so that we end up with: glasgow-haskell-users For user discussions ghc-devs For developer discussions ghc-commits For automated commit messages from the git repositories ghc-builds For automated nightly build reports ghc-tickets For automated messages from trac We would remove cvs-ghc cvs-libraries cvs-other glasgow-haskell-bugs but leave the archives in place, and for now forwarding messages to cvs-* to ghc-devs, and glasgow-haskell-bugs to ghc-tickets. (cvs-libraries and cvs-other are included in this list, because we think they are mainly used by libraries that GHC HQ maintains, or by GHC's lagging repos of libraries that other people maintain). The initial subscriber lists for ghc-devs, ghc-commits and ghc-builds would be the union of the subscribers of cvs-ghc, cvs-libraries and cvs-other. For ghc-tickets it would be the subscriber list for glasgow-haskell-bugs. Does that sound reasonable? Does anyone have any further questions or comments? Thanks Ian ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users ___ Cvs-ghc mailing list cvs-...@haskell.org http://www.haskell.org/mailman/listinfo/cvs-ghc ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: Mailing list reorganisation
On Tue, Dec 11, 2012 at 7:04 AM, Ian Lynagh i...@well-typed.com wrote: Does that sound reasonable? Does anyone have any further questions or comments? Sound good to me. Thanks for working on this. -- Johan ___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: Mailing list reorganisation
Good plan! Ian Lynagh i...@well-typed.com: Hi all, Following a recent discussion, we propose to reorganise the GHC-related mailing lists so that we end up with: glasgow-haskell-users For user discussions ghc-devs For developer discussions ghc-commits For automated commit messages from the git repositories ghc-builds For automated nightly build reports ghc-tickets For automated messages from trac We would remove cvs-ghc cvs-libraries cvs-other glasgow-haskell-bugs but leave the archives in place, and for now forwarding messages to cvs-* to ghc-devs, and glasgow-haskell-bugs to ghc-tickets. (cvs-libraries and cvs-other are included in this list, because we think they are mainly used by libraries that GHC HQ maintains, or by GHC's lagging repos of libraries that other people maintain). The initial subscriber lists for ghc-devs, ghc-commits and ghc-builds would be the union of the subscribers of cvs-ghc, cvs-libraries and cvs-other. For ghc-tickets it would be the subscriber list for glasgow-haskell-bugs. Does that sound reasonable? Does anyone have any further questions or comments? Thanks Ian ___ Glasgow-haskell-users mailing list glasgow-haskell-us...@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users ___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: Mailing list reorganisation
On Tue, Dec 11, 2012 at 7:04 AM, Ian Lynagh i...@well-typed.com wrote: Does that sound reasonable? Does anyone have any further questions or comments? Sound good to me. Thanks for working on this. -- Johan ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: Mailing list reorganisation
Good plan! Ian Lynagh i...@well-typed.com: Hi all, Following a recent discussion, we propose to reorganise the GHC-related mailing lists so that we end up with: glasgow-haskell-users For user discussions ghc-devs For developer discussions ghc-commits For automated commit messages from the git repositories ghc-builds For automated nightly build reports ghc-tickets For automated messages from trac We would remove cvs-ghc cvs-libraries cvs-other glasgow-haskell-bugs but leave the archives in place, and for now forwarding messages to cvs-* to ghc-devs, and glasgow-haskell-bugs to ghc-tickets. (cvs-libraries and cvs-other are included in this list, because we think they are mainly used by libraries that GHC HQ maintains, or by GHC's lagging repos of libraries that other people maintain). The initial subscriber lists for ghc-devs, ghc-commits and ghc-builds would be the union of the subscribers of cvs-ghc, cvs-libraries and cvs-other. For ghc-tickets it would be the subscriber list for glasgow-haskell-bugs. Does that sound reasonable? Does anyone have any further questions or comments? Thanks Ian ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
[Haskell-cafe] Re: mailing list choices?
Did Yahoo Google groups add support for NNTP yet? In past this did not work. If it still does not work then this would be one reason to prefer something which works with gmane. Peter. ___ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
Re: mailing list trouble
The haskell.org server was replaced on Sat with a new machine. Although care was taken to migrate all the files it looks like we missed some. The good news is the old server is still available and most likely has the missing archives. I'll work on restoring the missing ones today. -Mark Mark Wogahn / [EMAIL PROTECTED] Workstation Support Services (WSS) Department of Computer Science 51 Prospect Street, New Haven, CT 06520 Phone: (203) 432-1264 Fax: (203) 432-0593 Nothing is static, everything is falling apart -Fight Club ___ Haskell mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/haskell
Re: mailing list trouble
David Feuer wrote: There seems to be something wrong with the February archives for several of the haskell.org mailing lists (in short, they have vanished). I tried to send a message about this to [EMAIL PROTECTED], but the message was rejected by the mailer daemon. Anyone here know anything about this? I don't know anything specifically about the above problem. But I do know that the physical machine that is haskell.org was upgraded over the weekend, and there were a few minor hiccups. I'll forward your message to the appropriate administrator and hopefully we can get it straightened out. -antony -- Antony Courtney Grad. Student, Dept. of Computer Science, Yale University [EMAIL PROTECTED] http://www.apocalypse.org/pub/u/antony ___ Haskell mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/haskell
Re: mailing list trouble (haskell.org upgrade)
We've just upgraded haskell.org to a much faster machine and we've been slowly trying to get everything back to normal. There are a lot of things to do and we tried to do them Saturday morning when nobody was watching but I'm afraid we didn't get everything back in place before we were noticed. Everything should be back to normal soon. Let me know if anything is amiss tomorrow. John ___ Haskell mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/haskell
RE: mailing list
I don't think there was a solution. At least, I'm still being mailed :-( I guess the administrators aren't paying much attention to what's going on... Poor job. Sorry, I've been away for a few days. 1. To remove yourself from this mailing list, mail "[EMAIL PROTECTED]" with the line "unsubscribe your-email-address". 2. If you have any problems, mail me directly at [EMAIL PROTECTED]. 3. Please don't send unsubscribe requests to everyone on this list - it just annoys lots of people. Thanks, Simon
RE: Mailing list (was: Re: Q: Threads in GHC's RTS)
Sven writes: P.S.: Something completely unrelated: Why is majordomo.haskell.org expanded to scarlet.cam.uk.eu.microsoft.com in the To:-field? IMHO this is a bad idea, e.g. when people cut-and-paste this into their address books and scarlet is renamed to e.g. rhett. :-) We're working on fixing this at the moment. Whoever set up the DNS info for majordomo.haskell.org at Yale set it up as an alias, rather than a real IP or an MX record, and that's the reason it gets resolved to the canonical name all the time. It looks like some more changes will have to happen - the lists will probably change to glasgow-haskell-what@haskell.org soon. Cheers, Simon
