
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

Good plan!
Ian Lynagh
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

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
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

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
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
: 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-ghc@haskell.org http://www.haskell.org/mailman/listinfo/cvs-ghc
participants (5)
-
Carter Schonwald
-
Ian Lynagh
-
Johan Tibell
-
Manuel M T Chakravarty
-
Niklas Larsson