On Wed, 2 Feb 2000, Greg Stein wrote: > In this particular case, I think the "patches mailing list" would be a > self-contained list discussing a *patch*. Sure, it could certainly migrate > to python-dev when appropriate, but I think the majority of the discussion > should stay on the patches list. Otherwise, we'd just be spamming the -dev > list as if the patches list didn't exist. I retract my suggestion. Have python-patch, python-patch-discuss (python-patch would be replied-to: python-patch-discuss) and keep python-dev as a clean list. This way, people could just subscribe to python-patch, and when they get a patch they're interested in, they could subscribe to the discuss mailing list. That way, people could also subscribe to python-patch-discuss without subscribing to python-patch, to avoid the large attachments that would be sent by python-patch. Of course, mailman's new feature would automatically extract those attachments and post them up, so they can be downloaded by non-subscribers. enough-with-the-blabber-let's-just-get-something-going-ly y'rs, Z. -- Moshe Zadka <mzadka@geocities.com>. INTERNET: Learn what you know. Share what you don't.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4