This is in preparation for generating the former automatically
from the latter.
* admin/notes/bugtracker, admin/notes/copyright, admin/notes/newfile:
ChangeLog -> change log
* admin/notes/changelogs: Remove, merging old contents to ...
* admin/notes/repo: ... here.
* doc/emacs/maintaining.texi (Change Log): Mention that ChangeLog files may
be copied to or from a version control system.
* doc/emacs/trouble.texi (Sending Patches): Point to the commit messages.
* doc/lispref/intro.texi (Acknowledgments): ChangeLog file -> change log entries.
* doc/lispref/tips.texi (Library Headers): Emacs uses a version control system.
* etc/CONTRIBUTE: Give advice about git commit messages and how
to generate proposed patches containing them.
All bzr revision IDS, and all CVS revision IDs for which a commit
could be identified, were changed to time-date!committer version
stamps. All .cvsignore files in the history became .gitignore files.
Fixes-bug annotations from bzr were copied into the corresponding
commit comments.
(The first .cvsignore commit was 1999-09-30T14:07:54Z!fx@gnu.org>.
The last CVS commit was <2009-12-27T08:11:12Z!cyd@stupidchicken.com>)
Committer/author email addresses are generally correct for the
transition day, not necessarily when the commit was originally made.
See http://lists.gnu.org/archive/html/emacs-devel/2009-12/msg00758.html
* emacs.c (REPORT_EMACS_BUG_PRETEST_ADDRESS): Set it to
bug-gnu-emacs rather than emacs-pretest-bug.
* mail/emacsbug.el (report-emacs-bug-pretest-address): Set
it to bug-gnu-emacs rather than emacs-pretest-bug.
* CONTRIBUTE, NEWS: Use bug-gnu-emacs rather than emacs-pretest-bug
for bug reports for development versions.
* trouble.texi (Checklist): Use bug-gnu-emacs rather than
emacs-pretest-bug for bug reports for development versions.
* emacs-pretesters, make-announcement: Use bug-gnu-emacs rather
than emacs-pretest-bug for bug reports for development versions.
* INSTALL.BZR, README: Use bug-gnu-emacs rather than emacs-pretest-bug
for bug reports for development versions.
