-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I would like for devs to be able to avoid the hassle of posting non-trivial changes they make to the wget-patches list. To my mind, there are two ways of accomplishing this:
1. Make wget-patches a list _only_ for submitting patches for consideration by devs, no longer with the additional purpose of communicating changes from the devs to the users. 2. Have svnmailer post any changes made to trunk or to release branches to wget-patches automatically. This means such announcements will no longer be limited to trivial changes. Note that I've asked dotsrc.org to implement the same non-subscriber authentication measures that are currently employed for the main wget list (as previously discussed), so hopefully the level of spam seen on wget-patches will be dramatically decreased. If using wget-patches to communicate changes that have been made is in fact still a useful thing, then option #2 would be best. However, it's not clear to me that a significant number of people are actually reading wget-patches for this purpose, in which case any that do want to know about such changes are probably better off subscribing to wget-notify to see them, and I should employ option #1. Input welcome. :) - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGks7f7M8hyUobTrERCBgTAJ0VIi4Wd1Xq9DYQY95Hjoo1UXk5owCdECAX mdxQzH7DQD3pfYnM4YP8J8U= =gShz -----END PGP SIGNATURE-----
