[Python-Dev] A dizzying stream of checkins
Mon, 8 Apr 2002 16:50:48 -0400
>>>>> "GvR" == Guido van Rossum <firstname.lastname@example.org> writes:
GvR> Zope Corp uses a superior post-commit action script that seems
GvR> to be able to send email to different lists depending to the
GvR> tag; maybe we can add that feature to our commit script?
I think Ken wrote it, and it is very easy to configure. I've never
been able to figure out how the checkin -> email process works in much
detail, but the traffic_table.py script does what I want without
making me understand the details.
We could certainly split python-checkins into many lists:
python-checkins: checkins on the trunk
python-maint-checkins: checkins on maintenance branchs
python-other-checkins: everything else
This means that all-python-checkins == (python-checkins +
python-maint-checkins + python-other-checkins).
Perhaps there should be a separate doc checkin list, but I might be
happy leaving them in with the rest of the checkins.
Then we could add some specific rules for little corners of the CVS
tree. Like nondist/sandbox/ast could be sent to the compiler-sig.