I have often wondered if it would not be more appropriate if bf-committers<br>and blender-cvs were "read only" for people like myself that have no commit rights.<br>There are many other ways of communicating your issues to devs via irc or the .org
<br>forums even the bug tracker. <br><br><div><span class="gmail_quote">On 6/2/07, <b class="gmail_sendername">Joe Eagar</b> <<a href="mailto:joeedh@gmail.com">joeedh@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Chris Burt wrote:<br>> I, for one, am not signed up to this list to get mails full of<br>> people's compile errors. My personal opinion is that there should<br>> either be a list specifically dedicated to troubleshooting Blender, or
<br>> that we need to find someone to step forward for support on each<br>> individual platforms. The former sounds easier than the latter.<br>><br>I mentioned this (though, erm I was a little bit more. . .tactful :) ) a
<br>while back. The consensus seemed to be that compile errors should be on<br>the main list because they relate directly to development. And<br>truthfully I just don't read them anymore, other then a quick scan to<br>
see if any of my code is the problem.<br><br>Joe<br>_______________________________________________<br>Bf-committers mailing list<br><a href="mailto:Bf-committers@blender.org">Bf-committers@blender.org</a><br><a href="http://lists.blender.org/mailman/listinfo/bf-committers">
http://lists.blender.org/mailman/listinfo/bf-committers</a><br></blockquote></div><br>