From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
Cc: emacs-devel@gnu.org
Subject: Re: authors excludes the lisp manual.
Date: Thu, 12 May 2005 17:32:30 +0200 [thread overview]
Message-ID: <87ll6kbgtt.fsf@xs4all.nl> (raw)
In-Reply-To: <E1DWF51-0002PQ-4D@fencepost.gnu.org> (Richard Stallman's message of "Thu, 12 May 2005 10:54:27 -0400")
Richard Stallman <rms@gnu.org> writes:
> Does anybody know why authors in lisp/emacs-lisp/authors.el doesn't
> parse ChangeLogs in lispref/? I'd like to change that.
>
> Perhaps it has not been updated since we put lispref/ into the Emacs
> distribution.
It explicitly excludes lispref/:
,----
| (dolist (log logs)
| (when (and (string-match "ChangeLog\\(.[0-9]+\\)?$" log)
| (not (string-match "/lispref/" log)))
| (message "Scanning %s..." log)
| (authors-scan-change-log log table)))
`----
I guess that lispref/ was put in Emacs' CVS before the 21.1 release so
that authors needed to exclude it as Emacs 21 wasn't distributed with
the lisp manual.
> Maybe there are other dirs it doesn't cover, too. Could you check?
lispref/ is the only excluded dir. Shall I commit the patch below?
Lute.
Index: lisp/emacs-lisp/authors.el
===================================================================
RCS file: /cvsroot/emacs/emacs/lisp/emacs-lisp/authors.el,v
retrieving revision 1.21
diff -c -r1.21 authors.el
*** lisp/emacs-lisp/authors.el 8 Apr 2005 11:54:57 -0000 1.21
--- lisp/emacs-lisp/authors.el 12 May 2005 14:14:48 -0000
***************
*** 1,6 ****
;;; authors.el --- utility for maintaining Emacs' AUTHORS file -*-coding: iso-2022-7bit;-*-
! ;; Copyright (C) 2000, 2003 Free Software Foundation, Inc.
;; Author: Gerd Moellmann <gerd@gnu.org>
;; Maintainer: Kim F. Storm <storm@cua.dk>
--- 1,6 ----
;;; authors.el --- utility for maintaining Emacs' AUTHORS file -*-coding: iso-2022-7bit;-*-
! ;; Copyright (C) 2000, 2003, 2005 Free Software Foundation, Inc.
;; Author: Gerd Moellmann <gerd@gnu.org>
;; Maintainer: Kim F. Storm <storm@cua.dk>
***************
*** 597,604 ****
(unless (file-exists-p (expand-file-name "src/emacs.c" root))
(error "Not the root directory of Emacs: %s" root))
(dolist (log logs)
! (when (and (string-match "ChangeLog\\(.[0-9]+\\)?$" log)
! (not (string-match "/lispref/" log)))
(message "Scanning %s..." log)
(authors-scan-change-log log table)))
(let ((els (authors-process-lines "find" root "-name" "*.el")))
--- 597,603 ----
(unless (file-exists-p (expand-file-name "src/emacs.c" root))
(error "Not the root directory of Emacs: %s" root))
(dolist (log logs)
! (when (string-match "ChangeLog\\(.[0-9]+\\)?$" log)
(message "Scanning %s..." log)
(authors-scan-change-log log table)))
(let ((els (authors-process-lines "find" root "-name" "*.el")))
next prev parent reply other threads:[~2005-05-12 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 0:34 authors excludes the lisp manual Lute Kamstra
2005-05-12 14:54 ` Richard Stallman
2005-05-12 15:32 ` Lute Kamstra [this message]
2005-05-12 16:11 ` David Kastrup
2005-05-13 16:08 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ll6kbgtt.fsf@xs4all.nl \
--to=lute.kamstra.lists@xs4all.nl \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).