From: Michael G. <mg...@te...> - 2006-05-02 13:20:51
|
> Here's a summary of the lists currently available, with notes on how > I would propose to rationalise them:-- >=20 > mingw-crosscompile: [abandon in favor of mingw-users] Agreed. > mingw-cvs: [CVS commit notification list: keep] Agreed. > mingw-dvlpr: [private list for mingw developers: keep] Agreed. > mingw-editor: [private list for mingw.org editors: keep or merge with mingw-dvlpr] IMO covered by mingw-dvlpr -- I suppose all mingw-editors are subscribed to mingw-dvlpr anyway and mingw-dvlpr isn't a high volume list. > mingw-msys: [public list for msys: keep or merge with mingw-users] I'm ambivalent too. IMO we do have the occasional discussion regarding msys on mingw-users=20 > mingw-notify: [package release list: keep] Keep or not, I'm ambivalent, but I'd suggest to forward this to mingw-users unless already done so. > mingw-patches: [public list for discussion of patches: keep] > but could benefit from better exposure, say on the > "SubmitPatches" page on the MinGWiki. Mostly agreed. Not sure wether it is actually in use though (is it ?) Maybe it could prove useful after being made more commonly known. > mingw-port: [public for discussion of mingwPORT stuff: used little and thus should be abandoned] Agreed > mingw-users: [THE mingw list: keep] Well, yes :-) I do almost fully agree with your opinion, best, Michael =2D-=20 Vote against SPAM - see http://www.politik-digital.de/spam/ Michael Gerdau email: mg...@te... GPG-keys available on request or at public keyserver |