From 34bc62b98ef6a4c69474e84a8bcd0292a5e0e69e Mon Sep 17 00:00:00 2001 From: John Gilmore Date: Wed, 16 Nov 1994 00:23:04 +0000 Subject: [PATCH] M-x add-change --> M-x add-change-log-entry --- doc/standards.texi | 5 +++-- standards.texi | 5 +++-- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/doc/standards.texi b/doc/standards.texi index d2300c1c..6af8bc37 100644 --- a/doc/standards.texi +++ b/doc/standards.texi @@ -3,7 +3,7 @@ @setfilename standards.info @settitle GNU Coding Standards @c UPDATE THIS DATE WHENEVER YOU MAKE CHANGES! -@set lastupdate 10 November 1994 +@set lastupdate 15 November 1994 @c %**end of header @ifinfo @@ -197,7 +197,8 @@ can help eliminate conceptual inconsistencies between different parts of a program; they can give you a history of how the conflicting concepts arose. -Use the Emacs command @kbd{M-x add-change} to start a new entry in the +Use the Emacs command @kbd{M-x add-change-log-entry} to start a new +entry in the change log. An entry should have an asterisk, the name of the changed file, and then in parentheses the name of the changed functions, variables or whatever, followed by a colon. Then describe the changes diff --git a/standards.texi b/standards.texi index d2300c1c..6af8bc37 100644 --- a/standards.texi +++ b/standards.texi @@ -3,7 +3,7 @@ @setfilename standards.info @settitle GNU Coding Standards @c UPDATE THIS DATE WHENEVER YOU MAKE CHANGES! -@set lastupdate 10 November 1994 +@set lastupdate 15 November 1994 @c %**end of header @ifinfo @@ -197,7 +197,8 @@ can help eliminate conceptual inconsistencies between different parts of a program; they can give you a history of how the conflicting concepts arose. -Use the Emacs command @kbd{M-x add-change} to start a new entry in the +Use the Emacs command @kbd{M-x add-change-log-entry} to start a new +entry in the change log. An entry should have an asterisk, the name of the changed file, and then in parentheses the name of the changed functions, variables or whatever, followed by a colon. Then describe the changes