Update mailing list links to new Google Groups.

BUGFORM

@@ -4,7 +4,7 @@
 
 
 	If you find a bug please fill this form and send it to
-wmaker-dev@lists.windowmaker.org Please, USE THIS FORM!!!
+wmaker-dev@googlegroups.com Please, USE THIS FORM!!!
 
 0. Before reporting this bug I already:
 [ ] read the NEWS, README and INSTALL files

README

@@ -129,8 +129,8 @@ HELP ME!!!
 ==========
 
 There is a mailing list for discussing Window Maker at
-wmaker-user@lists.windowmaker.org To subscribe to it, send a message to
-wmaker-user-subscribe@lists.windowmaker.org
+wmaker-user@googlegroups.com.  To subscribe to it, visit
+https://groups.google.com/forum/#!forum/wmaker-user
 
 If you got a problem, ask there (after reading the docs, of course). The people
 there is more likely to be able to answer your questions than we are.  For bug
@@ -311,5 +311,5 @@ project. The name of people who have helped with localization (translation) can
 be found in po/README and Window Maker/README
 
 If you have any comments, fixes and bug reports (filled BUGFORMs) send them
-to wmaker-dev@lists.windowmaker.org
+to wmaker-dev@googlegroups.com
 

The-perfect-Window-Maker-patch.txt

@@ -134,7 +134,7 @@ Sending the patch to the mailing list
 
 Send your patches to:
 
-wmaker-dev@lists.windowmaker.org
+wmaker-dev@googlegroups.com
 
 Please do not send patches to any individual developer unless you have a very
 good reason to avoid more people being able to comment (and improve) on your
@@ -147,7 +147,7 @@ you, otherwise you may face the problems below. Doing this is really easy:
 #   (of course, replace smtp.example.com with your ISP's)
 git config --global sendemail.smtpserver "smtp.example.com"
 git config --global sendemail.validate   true
-git config sendemail.to "Window Maker Devel <wmaker-dev@lists.windowmaker.org>"
+git config sendemail.to "Window Maker Devel <wmaker-dev@googlegroups.com>"
 
 # If you're sending more than 1 patch, you may be interested in having an
 # introduction mail for the batch:

configure.ac

@@ -34,7 +34,7 @@ AC_PREREQ([2.69])
 
 dnl Configuration for Autoconf and Automake
 dnl =======================================
-AC_INIT([WindowMaker],[0.95.8],[wmaker-dev@lists.windowmaker.org],[WindowMaker],[http://www.windowmaker.org/])
+AC_INIT([WindowMaker],[0.95.8],[wmaker-dev@googlegroups.com],[WindowMaker],[http://www.windowmaker.org/])
 AC_CONFIG_MACRO_DIR([m4])
 AC_CONFIG_HEADERS([config.h])
 
@@ -370,7 +370,7 @@ AC_SEARCH_LIBS([strerror], [cposix])
 dnl nanosleep is generally available in standard libc, although not always the
 dnl case. One known example is Solaris which needs -lrt
 AC_SEARCH_LIBS([nanosleep], [rt], [],
-    [AC_MSG_ERROR([function 'nanosleep' not found, please report to wmaker-dev@lists.windowmaker.org])])
+    [AC_MSG_ERROR([function 'nanosleep' not found, please report to wmaker-dev@googlegroups.com])])
 
 dnl the flag 'O_NOFOLLOW' for 'open' is used in WINGs
 WM_FUNC_OPEN_NOFOLLOW

debian/copyright

@@ -1,6 +1,6 @@
 Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: wmaker
-Upstream-Contact: Window Maker developers mailing list <wmaker-dev@lists.windowmaker.org>
+Upstream-Contact: Window Maker developers mailing list <wmaker-dev@googlegroups.com>
 Source: http://repo.or.cz/w/wmaker-crm.git
 
 Files: *

doc/wmmenugen.1

@@ -73,7 +73,7 @@ with the unclear error message about
 you encountered a limitation of
 .BR wmmenugen .
 It would be a good idea to prepare an archive with the files incriminated and submit them to the
-mailing list (wmaker-dev@lists.windowmaker.org) with you command line, so the team can work on
+mailing list (wmaker-dev@googlegroups.com) with you command line, so the team can work on
 improving the behaviour of the program on this case.
 .SH "SEE ALSO"
 .BR wmgenmenu (1),