* lisp/message.el (format-alist): Change REGEXP.

[elisp/gnus.git-] / README.semi

diff --git a/README.semi b/README.semi
index d97306d..b297fe7 100644 (file)
--- a/README.semi
+++ b/README.semi
@@ -11,8 +11,8 @@ Gnus to use it, and you must not use gnus-mime for SEMI.
 before to install it.
 
 
-How to get?
-===========
+How to get? (via CVS)
+=====================
 
 (0) cvs login
 
@@ -23,44 +23,73 @@ How to get?
 
 (1) checkout
 
-    Please do following in a directory to extract (ex. site-lisp):
-
     % cvs -d :pserver:anonymous@chamonix.jaist.ac.jp:/hare/cvs/root \
-       co -r semi-gnus gnus
+       checkout [-r TAG] gnus
 
 (2) compile
 
-    ;; as same as Gnus
-
     % cd gnus
-
     % make EMACS=<file name of your emacs>
 
 (3) update
 
-    Please do following in your Open gnus directory:
+    % cvs update [-r TAG]
+
+Major tags are following:
+
+    semi-gnus          assigned to the latest stable version.  It is
+                       very conservative.
+
+    for-semi-N1_N2     assigned to the latest stable version for SEMI 
+                       API N1.N2 (N1 and N2 are natural number).
+                       (e.g. `for-semi-1_3' is for SEMI API 1.3)
+
+    gnus-N1_N2_N3      assigned to gnus(Gnus) N1.N2.N3
+                       (e.g. `gnus-6_2_1' means gnus 6.2.1).
+
+    larsi              Original Gnus
+
+    himi               himi branch
 
-    % cvs update -r semi-gnus
+    ichikawa           ichikawa branch
+
+    akr                        akr branch
+
+    shuhei-k           shuhei-k branch
+                       Mail-Followup-To/Mail-Reply-To, gnus-cache fix.
+
+
+How to get? (via ftp)
+=====================
+
+  Semi-daily snapshots are also available from
+
+    ftp://ftp.jaist.ac.jp/pub/GNU/elisp/semi-gnus/
+
+  NOTE: These snapshots are automatically created from our repository
+if something was changed within a day, and will usually not be tested.
 
 
 How to join development
 =======================
 
-  If you write bug-reports and/or suggestions for improvement, please
-send them to the tm Mailing List:
+  If you have found a bug in Gnus proper, please do `M-x gnus-bug' and
+send a bug report to the Gnus maintainers.
+
+  If you have found a bug in Semi-gnus, or if you're not sure whether it
+is a Gnus proper, please send a bug report to the Semi-gnus mailing list:
 
-       bug-tm-en@chamonix.jaist.ac.jp  (English)
-       bug-tm-ja@chamonix.jaist.ac.jp  (Japanese)
+    semi-gnus-en@meadow.scphys.kyoto-u.ac.jp   (English)
+    semi-gnus-ja@meadow.scphys.kyoto-u.ac.jp   (Japanese)
 
-  Via the tm ML, you can report SEMI related bugs, obtain the latest
-release of SEMI, and discuss future enhancements to SEMI.  To join the
-tm ML, send e-mail to
+Suggestions for Semi-gnus improvements are also welcome.
 
-       tm-ja-admin@chamonix.jaist.ac.jp        (Japanese)
-       tm-en-admin@chamonix.jaist.ac.jp        (English)
+  Via the Semi-gnus ML, you can report Semi-gnus related bugs, obtain
+the latest release of Semi-gnus, and discuss future enhancements to
+Semi-gnus.  To join the Semi-gnus ML, send an empty e-mail to
 
-  Since the user registration is done manually, please write the mail
-body in human-recognizable language (^_^).
+    semi-gnus-en-help@meadow.scphys.kyoto-u.ac.jp      (English)
+    semi-gnus-ja-help@meadow.scphys.kyoto-u.ac.jp      (Japanese)
 
   In addition, we need developers.  If you would like to develop it,
 please send mail to cvs@chamonix.jaist.ac.jp.