On Wed, Jun 21, 2000 at 01:51:26PM -0400, Jeremy Hylton wrote:
"TP" == Tim Peters firstname.lastname@example.org writes:
TP> + This mailing list doesn't work. At least the SourceForge I agree that it's a complete mess, though.
While you're all admiring the difficulty of the problem, how about actually checking in the pythonrun.c patch, assuming it's reasonable?
Frankly, I don't think the current mailing list is broken, *as long as patches are handled with reasonable speed* so that the backlog doesn't build up. That hasn't been done, and I don't understand why. Obviously the CNRI->BeOpen transaction resulted in some downtime for everyone, but now it's a month later and there's still stagnation. Why aren't incoming patches being handled now? It's not like there are very many patches per day; an hour or two should suffice to keep the queue from growing.
At this point, the best fix is to do two things:
1) Someone downloads the mbox archives of the patches list, and goes through all the past patches: apply them, discard them, send them back for revision.
2) Commit to handling new patches that arrive, and either apply/discard/revise them.
Worrying about patch management mechanism, while more patches pile up and are ignored in the meantime, is not going to help and will just results in continued stagnation. </flame>