wmbiff: Update FAQ.

wmbiff/FAQ

@@ -1,8 +1,9 @@
 * Does WMBiff have a mailing list?
 
-Subscribe to wmbiff-devel@lists.sourceforge.net.
+There is no longer a WMBiff-specific mailing list, but it may be discussed
+on the Window Maker Developers mailing list, wmaker-dev@lists.windowmaker.org.
 
-echo "subscribe wmbiff-devel" | mail majordomo@lists.sourceforge.net
+See http://lists.windowmaker.org/.
 
 * Why doesn't WMBiff update immediately after I read my mail?
 
@@ -35,14 +36,13 @@ If that doesn't work, run 'wmbiff -debug > wmbiff.log' and
 remove any passwords left in wmbiff.log.  Submit this log
 and your wmbiffrc (sanitized of passwords of course) using
 'reportbug' under Debian, or by sending mail to
-wmbiff-devel.
+wmaker-dev.
 
 * WMBiff doesn't do something I want. How do I suggest a feature?
 
 If using Debian, use 'reportbug wmbiff' and submit a
 wishlist bug.  Or, send mail with your suggestion to
-wmbiff-devel@lists.sourceforge.net.  Feature requests on
+wmaker-dev@lists.windowmaker.org.
-sourceforge don't get the same attention.
 
 Some previously requested features can't be done:
  - Count IMAP deleted messages separately (the protocol
@@ -58,7 +58,7 @@ Previously suggested features that are really hard:
 * I'm about to start writing a patch. How do I make sure it will
 get incorporated in WMBiff?
 
-Start a conversation on wmbiff-devel, and you'll probably
+Start a conversation on wmaker-dev, and you'll probably
 get some help.
 
 Tidbits:
@@ -74,52 +74,16 @@ Tidbits:
   - wmbiffrc.5.in
   - wmbiff.1
 
-* How do I get the very latest WMBiff from SourceForge CVS?
+* How do I get the very latest WMBiff from git?
 
-See http://sourceforge.net/cvs/?group_id=26389, or
+git clone http://repo.or.cz/dockapps.git
-http://sourceforge.net/projects/wmbiff then click on CVS.
+cd dockapps/wmbiff
-
-cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/wmbiff login
-cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/wmbiff co wmbiff
 
 * I added a feature to WMBiff. How do I submit a patch?
-** If you've modified code from a .tar.gz
- If you've modified a version of WMBiff downloaded from the web:
-  (in the wmbiff-x.x.x/wmbiff directory)
-  make indent
-  cd ..
-  make distclean
-  cd ..
-  mv wmbiff-x.x.x wmbiff-changed
-  tar xvfz wmbiff-x.x.x.tar.gz
-  diff --unified --recursive --new-file wmbiff-x.x.x wmbiff-changed > my-patch
-** If you've modified code from CVS
-  (in the wmbiff/wmbiff directory)
-  make indent
-  cd ..
-  [ optionally 'make distcheck' ]
-  make maintainer-clean
-  cvs update -d
-  [ resolve any conflicts ]
-  cvs diff -u | less     [ make sure the differences are roughly correct ]
-  cd ..
-  mv wmbiff wmbiff-changed
-  [ now checkout a new copy of wmbiff ]
-  diff --unified --recursive --new-file --exclude CVS wmbiff wmbiff-changed > my-patch
-
-** Sending the patch
-Submit my-patch as an attachment to mail sent to
-wmbiff-devel. Don't forget to subscribe to the mailing list
-so that we can discuss your patch.  This is roughly the same
-procedure you'll use to submit patches to any code, although
-others may not have the 'make indent' step.
 
+Submit patches in the same way as you would patches for Window Maker.  See:
+http://repo.or.cz/w/wmaker-crm.git/blob/HEAD:/The-perfect-Window-Maker-patch.txt
 
 * This FAQ is wrong.
 
-Send mail to wmbiff-devel@lists.sourceforge.net.
+Send mail to wmaker-dev@lists.windowmaker.org.
-
-;;; Local Variables: ***
-;;; mode: outline ***
-;;; End: ***
-