[Nmh-commits] CVS: nmh/docs README.SASL, 1.1, 1.2 FAQ, 1.2, 1.3 README.developers, 1.20, 1.21

[Ken Hornstein <address@hidden>]

Update of /cvsroot/nmh/nmh/docs
In directory subversions:/tmp/cvs-serv2428/docs

Modified Files:
        FAQ README.developers 
Added Files:
        README.SASL 
Log Message:
Merge in changes from the 1.1 branch.



Index: FAQ
===================================================================
RCS file: /cvsroot/nmh/nmh/docs/FAQ,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -r1.2 -r1.3
*** FAQ 12 Jun 2000 18:11:42 -0000      1.2
--- FAQ 5 Sep 2003 21:07:49 -0000       1.3
***************
*** 19,24 ****
     Richard Coleman (address@hidden) started the nmh project.
     After he grew too busy to continue maintaining it, it was handed off
!    to the net at large. Doug Morris (address@hidden) is hosting the
!    mailing lists, web pages, and CVS repository for nmh now.
  
  4) Why did Richard start the nmh project?
--- 19,27 ----
     Richard Coleman (address@hidden) started the nmh project.
     After he grew too busy to continue maintaining it, it was handed off
!    to the net at large. Doug Morris (address@hidden) hosted the web
!    site and mailing lists, web pages, and CVS repository for a long
!    time.  More recently, the CVS repository has moved to Savannah
!    (http://savannah.gnu.org/projects/nmh) and Ken Hornstein 
!    (address@hidden) is the project maintainer.
  
  4) Why did Richard start the nmh project?
***************
*** 55,64 ****
  
      The latest version of nmh is available at
!     ftp://ftp.mhost.com/pub/nmh/nmh.tar.gz
  
  8) Where is the nmh web page?
  
      The nmh home page is located at
!     http://www.mhost.com/nmh/
  
  9) Where is the nmh mailing list?
--- 58,67 ----
  
      The latest version of nmh is available at
!     http://savannah.gnu.org/download/nmh
  
  8) Where is the nmh web page?
  
      The nmh home page is located at
!     http://savannah.gnu.org/projects/nmh/
  
  9) Where is the nmh mailing list?

Index: README.developers
===================================================================
RCS file: /cvsroot/nmh/nmh/docs/README.developers,v
retrieving revision 1.20
retrieving revision 1.21
diff -C2 -r1.20 -r1.21
*** README.developers   6 Feb 2001 04:28:04 -0000       1.20
--- README.developers   5 Sep 2003 21:07:49 -0000       1.21
***************
*** 18,22 ****
  If you wish to change the `configure' script or its related files, you'll need
  to first install GNU m4, available from <ftp://ftp.gnu.org/pub/gnu/m4/> and 
then
! GNU autoconf (<ftp://ftp.gnu.org/pub/gnu/autoconf/>).
  
  Most of the configure-related files are automatically generated.  The only 
files
--- 18,23 ----
  If you wish to change the `configure' script or its related files, you'll need
  to first install GNU m4, available from <ftp://ftp.gnu.org/pub/gnu/m4/> and 
then
! GNU autoconf (<ftp://ftp.gnu.org/pub/gnu/autoconf/>).  Nmh is currently using
! a minimum of autoconf 2.54.
  
  Most of the configure-related files are automatically generated.  The only 
files
***************
*** 26,64 ****
  view of the developers (and the autoconf script).
  
! If you do change acconfig.h or configure.in and want to `cvs commit' them, be
! sure to regenerate the output files and commit them as well.  The easiest way 
to
! regenerate the files is to simply run `make' -- it'll do the necessary calls 
of
! autoconf and autoheader and will do a `./config.status --recheck', which will
! exercise your new configure script.
! 
! When you commit the configure-related files, it's very important to commit 
them
! in the right order.  The timestamps on the files in the CVS archive are based 
on
! the current time at the moment they were committed -- the timestamps from the
! local files you commit are not copied over.  If you commit the files in the
! wrong order, you'll cause unnecessary calls of `autoconf' to occur when people
! try to `make' their copies of the latest CVS source.  These people may be
! end-users who don't have any interest in changing the configure-related files
! and don't have autoconf installed.  They'll be unable to make without playing
! around with `touch'.
! 
! The correct procedure to commit the configure-related files is:
! 
!     % cvs commit acconfig.h aclocal.m4 configure.in
!     % autoheader; autoconf; \date > stamp-h.in
!     % cvs commit config.h.in configure stamp-h.in
! 
! The reason for the three-step commit is that configure.in contains the RCS $Id
! keyword, so when you commit it, a new version is written locally.  Therefore,
! the autoconf regeneration should be held off until after the commit, or your
! local stamp-h.in will become out-of-sync with the CVS version (granted, not 
that
! big a deal).  For the second step, you're doing the same commands as a 
! `make reset' would do, but using that command would require extra configure 
runs
! to make Makefile be up-to-date.  The reason for the backslash on `date' is in
! case you have `date' aliased in your shell to use a nonstandard format.
! 
! If you haven't changed all the files noted above, just commit the ones you 
have
! changed, in the stated order (for instance, configure.in, then configure and
! stamp-h.in).
! 
  
  -------------------
--- 27,38 ----
  view of the developers (and the autoconf script).
  
! Note that the automatically generated autoconf files (such as config.h.in,
! stamp-h.in, and configure), are NOT kept in CVS.  Thus, when you check out
! a CVS tree, you need to do the following things before you can build
! anything:
! 
!       % autoheader
!       % autoconf
!       % date > stamp-h.in
  
  -------------------