Mercurial > emacs
changeset 30793:ea6025935730
(Authors): New node.
author | Eli Zaretskii <eliz@gnu.org> |
---|---|
date | Tue, 15 Aug 2000 08:23:20 +0000 |
parents | 97c0caec0a32 |
children | 4711c3854433 |
files | man/programs.texi |
diffstat | 1 files changed, 19 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/man/programs.texi Mon Aug 14 21:45:06 2000 +0000 +++ b/man/programs.texi Tue Aug 15 08:23:20 2000 +0000 @@ -68,6 +68,7 @@ * Hideshow:: Displaying blocks selectively. * Documentation:: Getting documentation of functions you plan to call. * Change Log:: Maintaining a change history for your program. +* Authors:: Maintaining an @file{AUTHORS} file. * Tags:: Go direct to any function in your program in one command. Tags remembers which file it is in. * Imenu:: Making buffer indexes as menus. @@ -1755,6 +1756,24 @@ Version control systems are another way to keep track of changes in your program and keep a change log. @xref{Log Buffer}. +@node Authors +@section @file{AUTHORS} files +@cindex @file{AUTHORS} file + + Programs which have many contributors usually include a file named +@file{AUTHORS} in their distribution, which lists the individual +contributions. Emacs has a special command for maintaining the +@file{AUTHORS} file that is part of the Emacs distribution. + +@findex authors + The @kbd{M-x authors} command prompts for the name of the root of the +Emacs source directory. It then scans @file{ChageLog} files and Lisp +source files under that directory for information about authors of +individual packages and people who made changes in source files, and +puts the information it gleans into a buffer named @samp{*Authors*}. +You can then edit the contents of that buffer and merge it with the +exisiting @file{AUTHORS} file. + @node Tags @section Tags Tables @cindex tags table