------------------------------------------------------------
revno: 1058
committer: Mark Sapiro <[EMAIL PROTECTED]>
branch nick: 2.1
timestamp: Tue 2008-03-11 08:42:34 -0700
message:
  Merged A.M. Kuchling's 'Small Fixes' branch
modified:
  FAQ
  INSTALL
  NEWS
  README
  STYLEGUIDE.txt
  TODO
  UPGRADING
  messages/hu/README.hu
  messages/ja/README
    ------------------------------------------------------------
    revno: 1052.1.9
    committer: A.M. Kuchling <[EMAIL PROTECTED]>
    branch nick: 2.1-fixes
    timestamp: Fri 2008-03-07 12:49:59 -0500
    message:
      Docs are no longer in admin/www, but in doc/
    modified:
      INSTALL
      NEWS
      README
      messages/hu/README.hu
      messages/ja/README
    ------------------------------------------------------------
    revno: 1052.1.8
    committer: A.M. Kuchling <[EMAIL PROTECTED]>
    branch nick: 2.1-fixes
    timestamp: Fri 2008-03-07 12:44:50 -0500
    message:
      Merge
    modified:
      bin/add_members
      bin/clone_member
      bin/newlist
      bin/sync_members
    ------------------------------------------------------------
    revno: 1052.1.7
    committer: A.M. Kuchling <[EMAIL PROTECTED]>
    branch nick: 2.1-fixes
    timestamp: Fri 2008-03-07 12:43:35 -0500
    message:
      Merge NEWS change
    modified:
      NEWS
    ------------------------------------------------------------
    revno: 1052.1.6
    committer: A.M. Kuchling <[EMAIL PROTECTED]>
    branch nick: 2.1-fixes
    timestamp: Wed 2008-03-05 14:42:58 -0500
    message:
      According to http://wiki.list.org/display/DOC/Installation+requirements, 
Mailman no longer works with Python 2.1 or 2.2
    modified:
      README
    ------------------------------------------------------------
    revno: 1052.1.5
    committer: A.M. Kuchling <[EMAIL PROTECTED]>
    branch nick: 2.1-fixes
    timestamp: Tue 2008-02-26 13:52:39 -0500
    message:
      Correct Python version to 2.5.2; I forgot that 2.5.3 doesn't exist yet
    modified:
      README
    ------------------------------------------------------------
    revno: 1052.1.4
    committer: A.M. Kuchling <[EMAIL PROTECTED]>
    branch nick: 2.1-fixes
    timestamp: Tue 2008-02-26 13:45:38 -0500
    message:
      Remove references to README.{EXIM,QMAIL,LINUX}; grammar fix
    modified:
      FAQ
    ------------------------------------------------------------
    revno: 1052.1.3
    committer: A.M. Kuchling <[EMAIL PROTECTED]>
    branch nick: 2.1-fixes
    timestamp: Tue 2008-02-26 13:39:28 -0500
    message:
      Small grammar fixes; update reference to README.<mta> files
    modified:
      UPGRADING
    ------------------------------------------------------------
    revno: 1052.1.2
    committer: A.M. Kuchling <[EMAIL PROTECTED]>
    branch nick: 2.1-fixes
    timestamp: Tue 2008-02-26 13:33:22 -0500
    message:
      Update two URLs
    modified:
      STYLEGUIDE.txt
      TODO
    ------------------------------------------------------------
    revno: 1052.1.1
    committer: A.M. Kuchling <[EMAIL PROTECTED]>
    branch nick: 2.1-fixes
    timestamp: Tue 2008-02-26 13:29:03 -0500
    message:
      Update README
    modified:
      README

=== modified file 'FAQ'
--- a/FAQ       2005-08-27 01:40:17 +0000
+++ b/FAQ       2008-02-26 18:45:38 +0000
@@ -24,10 +24,11 @@
    turn off synchronous DNS resolution for messages originating from
    the local host.
 
-   In Exim, the value to edit is receiver_verify_hosts.  See
-   README.EXIM for details.  Other MTAs have (of course) different
-   parameters and defaults that control this.  First check the README
-   file for your MTA and then consult your MTA's own documentation.
+   In Exim, the value to edit is receiver_verify_hosts.  Consult the
+   Mailman Installation Manual for details.  Other MTAs have (of
+   course) different parameters and defaults that control this.  First
+   check the README file for your MTA and then consult your MTA's own
+   documentation.
 
 Q. My list members are complaining about Mailman's List-* headers!
    What can I do about this?
@@ -83,7 +84,7 @@
    (The distributed syslog.conf forwards the message to the loghost,
    when present.  See the syslog man page for more details.)
 
-   If your system is set like this, and you get a failure trying to
+   If your system is set up like this, and you get a failure trying to
    visit the mailman/listinfo web page, and it's due to a UID or GID
    mismatch, then you should get an entry at the end of
    /var/log/syslog identifying the expected and received values.
@@ -131,12 +132,7 @@
        From somebody Mon Oct  9 12:27:34 MDT 2000
 
    before every message and re-running the archive command
-   "bin/arch listname".  The archives should now exist.  See README.QMAIL
-   for more information.
-
-Q. Still having problems?  Running on GNU/Linux?
-
-A. See the README.LINUX file.
+   "bin/arch listname".  The archives should now exist.
 
 Q. I want to get rid of some messages in my archive.  How do I do
    this?

=== modified file 'INSTALL'
--- a/INSTALL   2005-08-27 01:40:17 +0000
+++ b/INSTALL   2008-03-07 17:49:59 +0000
@@ -6,13 +6,13 @@
 the Mailman Installation Guide.  Web, PostScript, PDF, and plaintext formats
 for this guide are available both within this source distribution and online.
 
-All manuals within this source distribution are provided in the admin/www
+All manuals within this source distribution are provided in the doc/
 directory:
 
-    HTML        : admin/www/mailman-install/index.html
-    PostScript  : admin/www/mailman-install.ps
-    PDF         : admin/www/mailman-install.pdf
-    plain text  : admin/www/mailman-install.txt
+    HTML        : doc/mailman-install/index.html
+    PostScript  : doc/mailman-install.ps
+    PDF         : doc/mailman-install.pdf
+    plain text  : doc/mailman-install.txt
 
 Or go online at http://www.list.org/site.html to find the online installation
 guide.

=== modified file 'NEWS'
--- a/NEWS      2008-03-06 20:34:12 +0000
+++ b/NEWS      2008-03-11 15:42:34 +0000
@@ -433,7 +433,7 @@
   Documentation
 
     - Most of the installation instructions have been moved to a latex
-      document.  See admin/www/mailman-install/index.html for details.
+      document.  See doc/mailman-install/index.html for details.
 
   Bug fixes and other patches
 
@@ -1947,7 +1947,7 @@
 
 2.0 release candidate 2 (10-Nov-2000)
 
-    - Documentation updates: start at admin/www/index.html
+    - Documentation updates: start in the doc/ directory.
 
     - bin/withlist accepts additional command line arguments when used
       with the --run flag; bin/mmsitepass and bin/newlist accept

=== modified file 'README'
--- a/README    2005-08-27 01:40:17 +0000
+++ b/README    2008-03-07 17:49:59 +0000
@@ -29,19 +29,15 @@
         http://www.gnu.org/software/mailman
         http://mailman.sf.net
 
-    Mailman 2.1 requires Python 2.1.3 or greater, which can be downloaded from:
+    Mailman 2.1 requires Python 2.3 or greater, which can be downloaded from:
 
         http://www.python.org
 
-    It is recommended that you use Python 2.3.3, the latest release as of this
-    writing (31-Dec-2003).  Update: 15-May-2004, the Python 2.3.4 release is
-    imminent, see:
-
-        http://www.python.org/2.3.4
-
-    Mailman will work with Python 2.2.3 as well, which is the latest release
-    on the Python 2.2 branch.  Mailman 2.1 is not compatible with Python 2.0
-    or any earlier version.
+    It is recommended that you use Python 2.5.2, the latest release as of this
+    writing (26-Feb-2008).  
+
+    Mailman 2.1 is not compatible with Python 2.2 or any earlier
+    version.
 
     You will also need an ANSI C compiler to build both Python and Mailman;
     gcc (the GNU C compiler) works just fine.  Mailman currently works only on
@@ -59,7 +55,7 @@
     Read the NEWS file for a list of changes since version 0.9.  Read the TODO
     file for our (extensive) wish list.  You can see Mailman 2.1 in action at:
 
-        http://mail.python.org/mailman-21/listinfo
+        http://mail.python.org/mailman/listinfo
 
     Mailman has most of the standard features you'd expect in a mailing list
     manager, and more:
@@ -118,7 +114,7 @@
 
     The online documentation can be found in
 
-        file:admin/www/index.html
+        file:doc/
 
     in the directory in which you unpacked Mailman.
 
@@ -131,7 +127,7 @@
     to help you get going with Mailman.
 
     Mailman-Users
-        An list for users of Mailman, for posting questions or problems
+        A list for users of Mailman, for posting questions or problems
         related to installation, use, etc.  We'll try to keep the deep
         technical discussions off this list.
 
@@ -146,22 +142,17 @@
         http://listowner.org
 
     Mailman-Announce
-        A read-only list for release announcements an other important news.
+        A read-only list for release announcements and other important news.
 
         http://mail.python.org/mailman/listinfo/mailman-announce
 
     Mailman-Developers
         A list for those of you interested in helping develop Mailman 2's
-        future direction.  This list will contain in-depth technical
+        future direction.  This list contains in-depth technical
         discussions.
 
         http://mail.python.org/mailman/listinfo/mailman-developers
 
-    Mailman3-Dev
-        Get involved now in the development of Mailman 3!
-
-        http://mail.python.org/mailman/listinfo/mailman3-dev
-
     Mailman-I18N
         A list for the discussion of the Mailman internationalization
         effort.  Mailman 2.1 is fully multi-lingual.
@@ -169,7 +160,7 @@
         http://mail.python.org/mailman/listinfo/mailman-i18n
 
     Mailman-Checkins
-        A read-only list which is an adjunct to the public anonymous CVS
+        A read-only list which is an adjunct to the Bazaar
         repository.  You can stay on the bleeding edge of Mailman development
         by subscribing to this list.
 

=== modified file 'STYLEGUIDE.txt'
--- a/STYLEGUIDE.txt    2004-05-15 22:02:13 +0000
+++ b/STYLEGUIDE.txt    2008-02-26 18:33:22 +0000
@@ -10,7 +10,7 @@
 Mailman.  In general, Guido van Rossum's style guide should be taken as a
 basis, as embodied in PEP 8:
 
-    http://www.python.org/peps/pep-0008.html
+    http://www.python.org/dev/peps/pep-0008/
 
 however, my (Barry Warsaw's) personal preferences differ from Guido's in a few
 places.  "When in Rome..." should apply meaning, when coding stuff for Python,

=== modified file 'TODO'
--- a/TODO      2005-08-27 01:40:17 +0000
+++ b/TODO      2008-02-26 18:33:22 +0000
@@ -12,7 +12,7 @@
 
     Please also see the Mailman design notes wiki at
 
-    http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
+    http://wiki.list.org/display/DEV/Home
 
 Email Handling
     - Re-implement the bulk mailer to do DNS lookups and remote MTA

=== modified file 'UPGRADING'
--- a/UPGRADING 2005-08-27 01:40:17 +0000
+++ b/UPGRADING 2008-02-26 18:39:28 +0000
@@ -38,7 +38,7 @@
     site before you upgrade.  BE SURE TO TURN OFF MAILMAN AS DESCRIBED ABOVE
     BEFORE YOU UPGRADE.
 
-    Specifically, in MM2.1.4 every message in the queues were represented by
+    Specifically, in MM2.1.4 every message in the queues was represented by
     two files, a .msg or .pck file containing the email message, and a .db
     file containing metadata about the message.  In MM2.1.5 this has been made
     more efficient by using only one file (with a .pck extension) for both the
@@ -74,7 +74,7 @@
 
     Check especially the values for (in Privacy -> Sender Filters)
     default_member_moderation, generic_nonmember_action, and
-    accept_these_nonmembers.  Check also the moderation flag on member
+    accept_these_nonmembers.  Also check the moderation flag on member
     accounts in the Membership Management screen.
 
     In Mailman 2.1, the qrunner subsystem has been completely
@@ -88,14 +88,14 @@
     pre-MM2.1alpha2 system to a post-MM2.1alpha2 system that you let
     the old qrunner process clear any and all messages sitting in the
     qfiles/ directory *BEFORE* you upgrade.  Otherwise after the
-    upgrade, those messages will not get delivered, and I'm not
-    exactly sure yet how to upgrade those pending messages.
+    upgrade, those messages will not get delivered, and there is no
+    easy way to upgrade those pending messages.
 
     NOTE: When upgrading to Mailman 2.1, you will need to regenerate
     your aliases files.  There have been many changes to the alias
     names, the programs they map to, and the name of the wrapper
-    script.  See README.<yourMTA> for details of making Mailman work
-    with your mail server.
+    script.  See the Mailman Installation Manual for details of making
+    Mailman work with your mail server.
 
     To regenerate your aliases, use the bin/genaliases script.
 
@@ -119,7 +119,7 @@
     Here are some instances we know about:
 
     - If you've applied patch #413752 (coerce to plaintext), then your
-      upgraded will not go smoothly.  Take a look at patch #651406 for
+      upgrade will not go smoothly.  Take a look at patch #651406 for
       an unofficial solution.
 
       http://sf.net/tracker/?group_id=103&atid=300103&func=detail&aid=413752

=== modified file 'messages/hu/README.hu'
--- a/messages/hu/README.hu     2005-08-27 01:40:17 +0000
+++ b/messages/hu/README.hu     2008-03-07 17:49:59 +0000
@@ -194,7 +194,7 @@
 
     Az online dokument���et�kicsomagolt Mailman k�t�an a
 
-        file:admin/www/index.html
+        file:doc/
 
     c�n.
 

=== modified file 'messages/ja/README'
--- a/messages/ja/README        2005-08-27 01:40:17 +0000
+++ b/messages/ja/README        2008-03-07 17:49:59 +0000
@@ -193,7 +193,7 @@
 
     �������� ���ʤ��� Mailman �򳫤����ǥ��쥯�ȥ����� 
-        file:admin/www/index.html
+        file:doc/
 
     ����äƤ��ޤ�.
 



--
Stable, maintained release series
https://code.launchpad.net/~mailman-coders/mailman/2.1

You are receiving this branch notification because you are subscribed to it.
_______________________________________________
Mailman-checkins mailing list
[email protected]
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-checkins/archive%40jab.org

Reply via email to