I am not a fan of it. It turns the dev-list into a spam list. The patches are not contextual enough for most people on the list to get value out of and therefore are not useful to the majority of folks. We have a separate list for that sort of commication that I think people can sign up for if they want to see this traffic.
On Wed, Jul 13, 2011 at 12:03 PM, Eric Merritt <[email protected]> wrote: > Guys, > > I am a big fan of patches going to the dev mailing list, in the style > of the git mailing list or the kernel. I think its a great way to > interact with the community and peers. I do this at in my professional > life and want to get back to it with open source projects. So I am > seriously considering moving back to pushing these through the this > mailing list. For those of you not wanting to receive them, each > commit email will have a tagged subject line in the form of > [*project-name* PATCH] and so should be easy to send off into your > bulk mail folder or trash. I figured I would poll the community, and > if people didn't explode startup with the next set of public patches > to one of the erlware projects. > > Eric > > -- > You received this message because you are subscribed to the Google Groups > "erlware-dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/erlware-dev?hl=en. > > -- Martin Logan Erlang & OTP in Action (Manning) http://manning.com/logan http://twitter.com/martinjlogan http://erlware.org -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
