New data on mailing lists

git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@41 b3059339-0415-0410-9bf9-f77b7e298cf2

DOCS/AUTHORS

@@ -34,9 +34,6 @@ Andreas Ackermann:  <asackerm@stud.informatik.uni-erlangen.de>
 - LIRC support (see DOCS/LIRC)
 - DGA support in libvo
 
-Dariusz Pietrzak: <dariush@ajax.umcs.lublin.pl>
-- mailing lists hosting (see README for details)
-
 Main testers:
   Gabucino
   Balazs Tibor (Tibcu)

DOCS/README

@@ -151,7 +151,7 @@ readme or other docs.
 You should try the latest test (pre) release version too, maybe your bug
 is already fixed, but the new version hasn't been released.
 If you couldn't solve the problem, then send a quality bugreport
-via E-Mail to the MPlayer-users list : mplayer@alan.umcs.lublin.pl
+via E-Mail to the MPlayer-users list : mplayer-users@lists.sourceforge.net
 
 *NEVER* send attached AVIs, MPEGs, or any big files to this list!!!
 Upload them to ftp://thot.banki.hu/incoming , and inform the list about
@@ -248,16 +248,13 @@ Homepage:  http://mplayer.sourceforge.net
 
 Mailing lists:
 ~~~~~~~~~~~~~~
-There are two public mailing lists on MPlayer. Subscribing can be achieved by
-writing to the following addresses, and specifying "subscribe" in the Subject,
-or message body.
+There are two public mailing lists on MPlayer. Subscribing can be achieved on
+the following addresses:
 
 - MPlayer-users
-       Write an e-mail to mplayer-request@alan.umcs.lublin.pl
+       http://lists.sourceforge.net/lists/listinfo/mplayer-users
 - MPlayer-announce
-       Write an e-mail to mplayer-announce-request@alan.umcs.lublin.pl
-
-Special thanks to Dariusz Pietrzak for the list hosting!
+       http://lists.sourceforge.net/lists/listinfo/mplayer-announce
 
 Standard Disclaimer:
 ~~~~~~~~~~~~~~~~~~~~

DOCS/mplayer.1

@@ -169,7 +169,7 @@ Just launch it! :)
 Possibly. Check DOCS.
 
 Bugreports should be addressed to the MPlayer-users mailing list
-(mplayer@alan.umcs.lublin.pl) ! If you want to submit a bugreport
+(mplayer-users@lists.sourceforge.net) ! If you want to submit a bugreport
 (which we love to receive!), please double-check the README, and
 tell us all that we need to know to identify your problem.