1 files changed, 1 insertions, 3 deletions
diff --git a/INSTALL.CVS b/INSTALL.CVS
index e21738d505c..80aa25e4278 100644
--- a/INSTALL.CVS
+++ b/INSTALL.CVS
@@ -21,9 +21,7 @@ directory tree.
 So if 'make bootstrap' fails, it may be necessary first to do 'make
 maintainer-clean' to clear out these stale files.  You can then try
-again, starting with `./configure'.  (Occasionally the loaddefs.el
+again, starting with `./configure'.
-file gets into a bad state due to changes in the Lisp libraries; this
-procedure forces it to be regenerated.)
 Normally, it is not necessary to use "make bootstrap" after every CVS
 update.  Unless there are problems, we suggest using the following

diff --git a/INSTALL.CVS b/INSTALL.CVS index e21738d505c..80aa25e4278 100644 --- a/INSTALL.CVS +++ b/INSTALL.CVS
@@ -21,9 +21,7 @@ directory tree.
21		21
22	So if 'make bootstrap' fails, it may be necessary first to do 'make	22	So if 'make bootstrap' fails, it may be necessary first to do 'make
23	maintainer-clean' to clear out these stale files. You can then try	23	maintainer-clean' to clear out these stale files. You can then try
24	again, starting with `./configure'. (Occasionally the loaddefs.el	24	again, starting with `./configure'.
25	file gets into a bad state due to changes in the Lisp libraries; this
26	procedure forces it to be regenerated.)
27		25
28	Normally, it is not necessary to use "make bootstrap" after every CVS	26	Normally, it is not necessary to use "make bootstrap" after every CVS
29	update. Unless there are problems, we suggest using the following	27	update. Unless there are problems, we suggest using the following