I'd also like to follow discussions, but unsubscribed from cvs-ghc due to the volume.<div><br></div><div>Maybe the reply-to field on cvs-ghc emails could be set to glasgow-haskell-bugs? (or whatever the agreed upon dev list is called)</div>
<div><br></div><div>Then if someone replies to a bot/commit message on cvs-ghc, it automatically goes to the place where active discussion happens, and those of us that don't want so many emails won't have to dig through cvs-ghc to find the interesting bits.</div>
<div><br></div><div>Andrew</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Dec 6, 2012 at 11:48 AM, Sean Leather <span dir="ltr"><<a href="mailto:leather@cs.uu.nl" target="_blank">leather@cs.uu.nl</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Dec 6, 2012 at 5:55 PM, Ian Lynagh wrote:<br><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Thu, Dec 06, 2012 at 06:25:49PM +0200, Roman Cheplyaka wrote:<br>
><br>
> +1. I'd like to follow GHC development discussions, but getting all the<br>
> commits is too much.<br>
<br>
</div>I'm surprised by this, FWIW. I think skimming the commits is a good way<br>
to get an idea of what's going on,</blockquote><div><br></div></div><div>Indeed, it can be. But I can't keep up with the huge number of commits everyday, and I'm not interested in the large majority of them.</div>
<div class="im"><div>
<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">while discussions between developers<br>
tend to be focussed on particular obscure points (e.g. discussing<br>
correctness of a murky corner in the intersection between 2 new type<br>
system extensions, or discussing the way PIC is handled on OSX/PowerPC)<br>
which I wouldn't have thought were of much interest to any party not<br>
involved in the discussion and familiar with the details.<br></blockquote><div><br></div></div><div>I find these things (both examples, actually) more interesting. I'm more likely to follow such threads than I am to skim the commits.</div>
<div class="im">
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Anyway, I'm not really too fussed about what mailing lists we have. I'll<br>
just subscribe to them all anyway :-)<br></blockquote><div></div></div></div><br><div>I'm not too fussed about it, either, but I wouldn't mind a restructuring. I might even subscribe to them all as well, but then it will be easier to follow the commits at a different pace from the rest (without having to create a new filter, which I've been so far too lazy to do).</div>
<div><br></div><div>Regards,</div><div>Sean</div>
<br>_______________________________________________<br>
Glasgow-haskell-users mailing list<br>
<a href="mailto:Glasgow-haskell-users@haskell.org">Glasgow-haskell-users@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/glasgow-haskell-users" target="_blank">http://www.haskell.org/mailman/listinfo/glasgow-haskell-users</a><br>
<br></blockquote></div><br></div>