On Mon, Apr 19, 2010 at 12:05 AM, Eli Barzilay <e...@barzilay.org> wrote: > In any case, I'll do a quick poll. I see the following options: > > 1. Leave things as they are now: the few people who wanted to get > notifications will continue getting them, nobody else will. > > 2. Create a new mailing list for commits, and have all comitters on it > (as well as anyone else who wants to be on it). Leave plt-dev > alone. > > 3. Send *summary* emails (=> only changed file lists and commit logs, > no diffs) to plt-dev. Doing this will require some solution for > people who want to get the diffs, but don't want to give up being > on plt-dev -- in this case they'll need to go through the hassle of > filtering the plt-dev messages out and keep the more detailed > messages. > > 4. Send the complete emails to plt-dev -- as I originally suggested. > This might get a little too verbose a few times (eg, large > commits), so it might require some adjusting. > > 5. Any other suggestion? (If you have a suggestion, then please reply > on the list, not directly to me.) > > -- > ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: > http://barzilay.org/ Maze is Life!
I vote for #2. There are clearly people interested in getting these messages, and there should be a standard way for anyone to get them. On the other hand, there are people generous enough to contribute their time and attention to plt-dev, and if they don't want a deluge of [what is to them] spam, they shouldn't have to put up with it from us. --Carl _________________________________________________ For list-related administrative tasks: http://list.cs.brown.edu/mailman/listinfo/plt-dev
