> Alas, a typical exchange. The checkins are mailed from the committer's > Sf email address, but the mailing list has been set up to redirect all > replies to python-dev -- if you don't catch this before sending, you > may be embarrassed in public or confuse the addressee. > > Is this behavior of the checkins list really a good idea?
I think it should be changed. In addition to making it a PITA to send notes to the committer, there is another issue. For anyone subscribing to python-dev but not the checkins list, they see conversations started without seeing the history of checkins that gave rise to those conversations. Worse, the resolution of those conversations is often another checkin (which doesn't get cc'd to python-dev so it is not obvious when there is a resolution). For instance, this thread was resolved by Michael's checkin, 2.137, but you wouldn't know that from reading python-dev. A few years ago, the cc to python-dev was not automatic and the default reply address was the original committer. That worked much better. Raymond P.S. I still don't follow the whole yours/mine comment from Michael. The offending code line was part of 2.136 which CVS says was checked-in by him on 5/27/2005 and then fixed by him on 6/30/2005. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
