Transports: pass back next id for continued-transport

[exim.git] / doc / doc-txt / dbm.discuss.txt

diff --git a/doc/doc-txt/dbm.discuss.txt b/doc/doc-txt/dbm.discuss.txt
index 7517c4b8882153de142aff6fd13f44fabc4fe9e9..50f0687137bb15e187c916de0c075e4b6e8a3cee 100644 (file)
--- a/doc/doc-txt/dbm.discuss.txt
+++ b/doc/doc-txt/dbm.discuss.txt
@@ -1,5 +1,3 @@
-$Cambridge: exim/doc/doc-txt/dbm.discuss.txt,v 1.1 2004/10/07 15:04:35 ph10 Exp $
-

 DBM Libraries for use with Exim
 -------------------------------
 
 DBM Libraries for use with Exim
 -------------------------------
 


@@ -43,7 +41,8 @@ some time, and various releases 2.x began to appear towards the end of 1997. In
 November 1999, version 3.0 was released, and the ending of support for 2.7.7,
 the last 2.x release, was announced for November 2000. (Support for 1.85 has
 already ceased.) There were further 3.x releases, but by the end of 2001, the
 November 1999, version 3.0 was released, and the ending of support for 2.7.7,
 the last 2.x release, was announced for November 2000. (Support for 1.85 has
 already ceased.) There were further 3.x releases, but by the end of 2001, the

-current release was 4.0.14.
+current release was 4.0.14.  In 2022 it was 5.3.28 on Linux (the then-owner
+has developed it further but Exim does not support anything after 5.x).

 
 There are major differences in implementation and interface between the DB 1.x
 and 2.x/3.x/4.x releases, and they are best considered as two independent dbm
 
 There are major differences in implementation and interface between the DB 1.x
 and 2.x/3.x/4.x releases, and they are best considered as two independent dbm


@@ -159,7 +158,7 @@ This dbm library can be called by Exim in one of two ways: via the ndbm
 compatibility interface, or via its own native interface. There are two
 advantages to doing the latter: (1) you don't run the risk of Exim's seeing the
 "wrong" version of the ndbm.h header, as described above, and (2) the
 compatibility interface, or via its own native interface. There are two
 advantages to doing the latter: (1) you don't run the risk of Exim's seeing the
 "wrong" version of the ndbm.h header, as described above, and (2) the

-performace is better. It is therefore recommended that you set USE_DB=yes in an
+performance is better. It is therefore recommended that you set USE_DB=yes in an

 appropriate Local/Makefile-xxx file. (If you are compiling for just one OS, it
 can go in Local/Makefile itself.)
 
 appropriate Local/Makefile-xxx file. (If you are compiling for just one OS, it
 can go in Local/Makefile itself.)
 


@@ -225,7 +224,7 @@ files in other formats that are created by other programs.
 Berkeley DB 4.x
 ---------------
 
 Berkeley DB 4.x
 ---------------
 

-The 4.x series is a developement of the 2.x and 3.x series, and the above
+The 4.x series is a development of the 2.x and 3.x series, and the above

 comments apply.
 
 
 comments apply.