Adding one more readme file. This one is intended to serve as some

kind of "howto" for the most notable incompatible configuration
changes.

diff --git a/Makefile.am b/Makefile.am
index 9c4d13b42633de64a77f885aabbed82272bcfd4d..8252c1957d5d9adf929aef5b10538baa0589ae59 100644 (file)
--- a/Makefile.am
+++ b/Makefile.am
@@ -66,7 +66,7 @@ EXTRA_DIST = COPYRIGHT GPL OPS OPS.PGP TODO configure acconfig.h attach.h \
        sort.h mime.types VERSION prepare _regex.h OPS.MIX      \
        README.SECURITY remailer.c remailer.h browser.h \
        lib.h extlib.c pgpewrap pgplib.h Muttrc.head Muttrc \
-       makedoc.c stamp-doc-rc README.SSL
+       makedoc.c stamp-doc-rc README.SSL README.UPGRADE
 
 
 mutt_dotlock_SOURCES = mutt_dotlock.c

diff --git a/README b/README
index dac2cb49dc88fd2848b2296d2f47b6be1c4a3118..6e1e88a053c0b921d00a008eddf0757cac659876 100644 (file)
--- a/README
+++ b/README
@@ -1,5 +1,5 @@
-README for mutt-0.95
-====================
+README for mutt-1.1
+===================
 
 If you got the mutt source code from the public CVS repository (CVS
 root: :pserver:anonymous@ftp.guug.de:/home/roessler/cvs, password
@@ -13,6 +13,9 @@ the last public version can be found under NEWS.
 
 PGP users should read doc/PGP-Notes.txt.
 
+Those who upgrade from a version of mutt prior to 1.1 should read
+the README.UPGRADE file.
+
 Before you start hacking on mutt, read doc/devel-notes.txt.  Before
 applying patches to mutt, read doc/applying-patches.txt.  Please,
 read these files, as they will save you from asking FAQs.

diff --git a/README.UPGRADE b/README.UPGRADE
new file mode 100644 (file)
index 0000000..5826ca0
--- /dev/null
+++ b/README.UPGRADE
@@ -0,0 +1,41 @@
+UPGRADING FROM MUTT 1.0
+-----------------------
+
+
+Please read the present document carefully when upgrading Mutt from
+version 1.0 to the current version.  It lists a couple of
+configuration changes you may wish to make in order to continue
+working with mutt.
+
+
+1. PGP support
+
+PGP support has changed.  Instead of a collection of hard-coded
+parameter strings, we use formats now to construct the invocation
+command lines for the various PGP versions.
+
+You can find sample configurations for the most popular PGP versions
+in the contrib/ directory.  You can customize them for your needs,
+or you can just source them from your .muttrc.
+
+
+2. Mailing list behaviour
+
+You may notice that the lists command "doesn't seem to work" any
+more.  If you didn't experience any problems with it using your old
+mutt version, just change "lists" to "subscribe" in your .muttrc.
+
+Otherwise, you may wish to make use of the distinction between known
+and subscribed lists mutt offers: When you know about a mailing list
+and want to include it with list-reply (say, for instance, the
+cypherpunks list), but aren't subscribed to it, declare it as known
+with "lists".  When you are subscribed to a list and want to
+generate Mail-Followup-To headers when writing to it, want to match
+messages coming from this list with the ~l pattern, and want to see
+the list address with the %L format on the index menu, "subscribe"
+it.
+
+Note that "subscribe" implies "lists", and "unlists" implies
+"unsubscribe" - every subscribed list is known.
+
+$Id$