mutt stable branch with some hacks
Update stale INSTALL+README files
+21
-26
+9
ChangeLog
+9
ChangeLog
···
1
+
2008-01-15 12:34 +0100 Rocco Rutte <pdmef@gmx.net> (c06891454c6e)
2
+
3
+
* mh.c: Make maildir_delayed_parsing() more readable
4
+
5
+
2008-01-15 11:58 +0100 Rocco Rutte <pdmef@gmx.net> (2d88a6996973)
6
+
7
+
* ChangeLog, init.h: Mention that References: and Date: cannot be
8
+
changed in editor (closes #1234).
9
+
1
10
2008-01-15 10:49 +0100 Rocco Rutte <pdmef@gmx.net> (ba0d96408425)
2
11
3
12
* UPDATING, globals.h, init.h, query.c: Make formatting of query menu
+4
-5
INSTALL
+4
-5
INSTALL
···
14
14
HP-UX
15
15
IRIX
16
16
Linux
17
+
Mac OS X
17
18
Atari MiNT
18
19
MkLinux
19
20
NetBSD
···
25
26
Ultrix
26
27
UnixWare
27
28
28
-
- If you are building from CVS, or if you are changing parts of mutt,
29
+
- If you are building from Mercurial, or if you are changing parts of mutt,
29
30
particularly the build system, do read doc/devel-notes.txt.
30
31
31
32
- An ANSI C compiler (such as GCC) is required.
···
54
55
Installing Mutt is rather painless through the use of the GNU
55
56
autoconf package. Simply untar the Mutt distribution, and run the
56
57
``configure'' script. If you have obtained the distribution from
57
-
the CVS repository, run the ``prepare'' script with the same command
58
+
the Mercurial repository, run the ``prepare'' script with the same command
58
59
line parameters you would pass to configure. It will set up mutt's
59
60
build environment and add the files which are present in the tar
60
-
balls, but not in the CVS repository.
61
+
balls, but not in the Mercurial repository.
61
62
62
63
In most cases, configure will automatically determine everything it
63
64
needs to know in order to compile. However, there are a few options
···
298
299
299
300
The system curses library is said to be badly broken. Use GNU
300
301
ncurses or SLang instead.
301
-
302
-
$Id$
+8
-21
README
+8
-21
README
···
1
1
README for mutt-1.5
2
2
===================
3
3
4
-
When updating mutt from an earlier release or from CVS, please make sure
5
-
to read the compatbility notes in ``UPDATING''.
4
+
When updating mutt from an earlier release or from Mercurial, please
5
+
make sure to read the compatibility notes in ``UPDATING''. Older changes
6
+
between mutt-1.2 and mutt-1.4 are listed in NEWS.
6
7
7
-
If you got the mutt source code from the public CVS repository (CVS
8
-
root: :pserver:anonymous@cvs.mutt.org:/home/roessler/cvs, password
9
-
anonymous), please read doc/devel-notes.txt to make sure that you
10
-
have a complete development environment.
8
+
If you got the mutt source code from the public Mercurial repository
9
+
(http://dev.mutt.org/hg/mutt/), please read doc/devel-notes.txt to make
10
+
sure that you have a complete development environment.
11
11
12
-
NOTE: The CVS repository now resides on a machine which is different
13
-
from ftp.mutt.org. Anonymous CVS from ftp.mutt.org does not work
14
-
any more.
15
-
16
-
Installation instructions are detailed in ``INSTALL''.
17
-
18
-
The user manual is in doc/manual.txt. A list of major changes since
19
-
the last public version can be found under NEWS.
20
-
21
-
PGP users should read doc/PGP-Notes.txt.
22
-
23
-
Those who upgrade from a version of mutt prior to 1.1 should read
24
-
the README.UPGRADE file.
12
+
Installation instructions are detailed in ``INSTALL''. The user manual
13
+
is in doc/manual.txt. PGP users should read doc/PGP-Notes.txt.
25
14
26
15
Before you start hacking on mutt, read doc/devel-notes.txt. Before
27
16
applying patches to mutt, read doc/applying-patches.txt. Please,
···
37
26
38
27
A list of mirror sites can be found under
39
28
<http://www.mutt.org/download.html>.
40
-
41
-
$Id$