merge from trunk

21 files changed, 1517 insertions, 1952 deletions

diff --git a/admin/notes/BRANCH b/admin/notes/BRANCH
deleted file mode 100644
index 9f09135f206..00000000000
--- a/admin/notes/BRANCH
+++ /dev/null
@@ -1,32 +0,0 @@
-You can view the available Emacs branches at
-
-http://bzr.savannah.gnu.org/r/emacs/
-
-Development normally takes places on the trunk.
-Sometimes specialized features are developed on separate branches
-before possibly being merged to the trunk.
-
-Development is discussed on the emacs-devel mailing list.
-
-Sometime before the release of a new major version of Emacs (eg 23.2),
-a "feature freeze" is imposed on the trunk.  No new features may be
-added after this point.  This is usually some months before the release.
-
-Shortly before the release, a release branch is created, and the
-trunk is then free for development.
-For example, "emacs-23" for Emacs 23.2 and later, "EMACS_23_1_RC" for
-23.1, "EMACS_22_BASE" for 22.x, and "EMACS_21_1_RC" for 21.x.
-
-Consult emacs-devel for exactly what kinds of changes are allowed
-on what branch at any time.
-
-If you are looking at this file in a branch other than the trunk,
-there may be some branch-specific documentation below this line.
-________________________________________________________________________
-
-* elpa
-
-  This branch does not contain a copy of Emacs, but of the Emacs Lisp
-  package archive (elpa.gnu.org).  See admin/notes/elpa for further
-  explanation, and the README file in the branch for usage
-  instructions.
diff --git a/admin/notes/bugtracker b/admin/notes/bugtracker
index 7947b17973b..fb65bbe4330 100644
--- a/admin/notes/bugtracker
+++ b/admin/notes/bugtracker
@@ -334,7 +334,7 @@ http://debbugs.gnu.org/cgi/pkgreport.cgi?users=emacs;tag=calendar
 *** To merge bugs:
 Eg when bad replies create a bunch of new bugs for the same report.
 Bugs must all be in the same state (e.g. same package(s) and severity
--- see `reassign' and `severity' below), but need not have the same
+-- see 'reassign' and 'severity' below), but need not have the same
 tags (tags are merged). E.g.:
 
 merge 123 124 125 ...
@@ -343,8 +343,8 @@ Note that merging does not affect titles.  In particular, a "retitle"
 of merged bugs only affects individual bugs, not all of them.
 
 *** Forcing a merge:
-Like `merge', but bugs need not be in the same state.  The packages
-must still match though (see `reassign' below).  The first one listed
+Like 'merge', but bugs need not be in the same state.  The packages
+must still match though (see 'reassign' below).  The first one listed
 is the master.  E.g.:
 
 forcemerge 123 124 125 ...
@@ -383,7 +383,7 @@ See http://debbugs.gnu.org/Developer#severities for the meanings.
 *** To set the owner of a bug:
 owner 123 A Hacker <none@example.com>
 
-The shorthand `!' means your own address.
+The shorthand '!' means your own address.
 
 *** To remove the owner of a bug:
 noowner 123
@@ -408,7 +408,7 @@ reassign 1234 emacs
 Note that reassigning clears the list of found versions, even if the
 new packages includes the original one.
 
-** To remove spam from the tracker, move it to the `spam' pseudo-package:
+** To remove spam from the tracker, move it to the 'spam' pseudo-package:
 reassign 123 spam
 
 (Should not be necessary any more, now that the input is moderated.)
@@ -463,68 +463,30 @@ time, rather than by increasing bug number
 
 "raw" = ?
 
-** ChangeLog issues
+** Change log issues
 
 *** When you fix a bug, it can be helpful to put the bug number in the
-ChangeLog entry, for example:
+change log entry, for example:
 
-   * foo.el (foofunc): Fix the `foo' case.  (Bug#123)
+   * lisp/menu-bar.el (menu-set-font): Doc fix.  (Bug#21303)
 
 Then the relevant bug can be found for easy reference.  If it's an
-obvious fix (e.g. a typo), there's no need to clutter the log with the
+obvious fix (e.g., a typo), there's no need to clutter the log with the
 bug number.
 
 Similarly, when you close a bug, it can be helpful to include the
-relevant ChangeLog entry in the message to the bug tracker, so people
+relevant change log entry in the message to the bug tracker, so people
 can see exactly what the fix was.
 
 *** bug-reference-mode
 
-Activate `bug-reference-mode' in ChangeLogs to get clickable links to
+Activate 'bug-reference-mode' in ChangeLogs to get clickable links to
 the bug web-pages.
 
 *** Debian stuff
 
 http://lists.gnu.org/archive/html/emacs-devel/2009-11/msg00440.html
 
-** Bazaar stuff
-
-*** You can use `bzr commit --fixes debbugs:123' to mark that a commit fixes
-Emacs bug 123.  You will first need to add a line to one of your
-configuration files, ~/.bazaar/bazaar.conf or ~/.bazaar/locations.conf:
-
-bugtracker_debbugs_url = http://debbugs.gnu.org/{id}
-
-Here "{id}" is a literal string, a placeholder that will be replaced
-by the bug number you specify after `--fixes debbugs:' in the bzr
-command line (123 in the example above).
-
-In the bazaar.conf file, this setting should go into the [DEFAULT]
-section.
-
-In the locations.conf file, it should go into the branch-specific
-configuration section for the branch where you want this to be in
-effect.  For example, if you want this to be in effect for the branch
-located at `/home/projects/emacs/trunk', you need to have this in your
-~/.bazaar/locations.conf file:
-
-[/home/projects/emacs/trunk]
-bugtracker_debbugs_url = http://debbugs.gnu.org/{id}
-
-If you want to use this in all Emacs branches whose common parent is
-`/home/projects/emacs', put the setting in the [/home/projects/emacs]
-section.  See "bzr help configuration" for more information about
-the *.conf files, their location and formats.  See "bzr help bugs" for
-more information about the bugtracker_debbugs_url setting.
-
-See also log-edit-rewrite-fixes in .dir-locals.el.
-
-Note that all this does is add some metadata to the commit, it doesn't
-actually mark the bug as closed in the tracker.  You can see this
-information with `bzr log', and it will show up as a link in a recent
-loggerhead installation, or with some of the graphical frontends to
-`bzr log'.
-
 ** Gnus-specific voodoo
 
 *** Put point on a bug-number and try: M-x gnus-read-ephemeral-emacs-bug-group
diff --git a/admin/notes/bzr b/admin/notes/bzr
deleted file mode 100644
index 8f7d0d94fa8..00000000000
--- a/admin/notes/bzr
+++ /dev/null
@@ -1,363 +0,0 @@
-NOTES ON COMMITTING TO EMACS'S BAZAAR REPO    -*- outline -*-
-
-* Install changes only on one branch, let them get merged elsewhere if needed.
-In particular, install bug-fixes only on the release branch (if there
-is one) and let them get synced to the trunk; do not install them by
-hand on the trunk as well.  E.g. if there is an active "emacs-23" branch
-and you have a bug-fix appropriate for the next Emacs-23.x release,
-install it only on the emacs-23 branch, not on the trunk as well.
-
-Installing things manually into more than one branch makes merges more
-difficult.
-
-http://lists.gnu.org/archive/html/emacs-devel/2010-03/msg01124.html
-
-The exception is, if you know that the change will be difficult to
-merge to the trunk (eg because the trunk code has changed a lot).
-In that case, it's helpful if you can apply the change to both trunk
-and branch yourself (when committing the branch change, indicate
-in the commit log that it should not be merged to the trunk; see below).
-
-* Backporting a bug-fix from the trunk to a branch (e.g. "emacs-23").
-Indicate in the commit log that there is no need to merge the commit
-to the trunk.  Anything that matches `bzrmerge-skip-regexp' will do;
-eg start the commit message with "Backport:".  This is helpful for the
-person merging the release branch to the trunk.
-
-http://lists.gnu.org/archive/html/emacs-devel/2010-05/msg00262.html
-
-* Installing changes from your personal branches.
-If your branch has only a single commit, or many different real
-commits, it is fine to do a merge.  If your branch has only a very
-small number of "real" commits, but several "merge from trunks", it is
-preferred that you take your branch's diff, apply it to the trunk, and
-commit directly, not merge.  This keeps the history cleaner.
-
-In general, when working on some feature in a separate branch, it is
-preferable not to merge from trunk until you are done with the
-feature.  Unless you really need some change that was done on the
-trunk while you were developing on the branch, you don't really need
-those merges; just merge once, when you are done with the feature, and
-Bazaar will take care of the rest.  Bazaar is much better in this than
-CVS, so interim merges are unnecessary.
-
-Or use shelves; or rebase; or do something else.  See the thread for
-yet another fun excursion into the exciting world of version control.
-
-http://lists.gnu.org/archive/html/emacs-devel/2010-04/msg00086.html
-
-* Installing changes from gnulib
-Some of the files in Emacs are copied from gnulib.  To synchronize
-these files from the version of gnulib that you have checked out into
-a sibling directory of your branch, type "make sync-from-gnulib"; this
-will check out the latest version of gnulib if there is no sibling
-directory already.  It is a good idea to run "bzr status" afterwards,
-so that if a gnulib module added a file, you can record the new file
-using "bzr add".  After synchronizing from gnulib, do a "make" in the
-usual way.
-
-To change the set of gnulib modules, change the GNULIB_MODULES
-variable in the top-level Makefile.in, and then run:
-
-  ./config.status
-  make sync-from-gnulib
-  bzr status
-
-The last command will mention files that may need to be added using
-"bzr add".  If you remove a gnulib module, or if a gnulib module
-removes a file, then remove the corresponding files by hand.
-
-* How to merge changes from emacs-23 to trunk
-
-The following description uses bound branches, presumably it works in
-a similar way with unbound ones.
-
-0) (This step is only necessary if using bzr older than 2.4.0.)
-Get the bzr changelog_merge plugin:
-
-cd ~/.bazaar/plugins
-bzr branch http://bazaar.launchpad.net/~spiv/bzr-changelog-merge/trunk changelog_merge
-
-This plugin should make merging ChangeLogs smoother.  It merges new
-entries to the top of the file, rather than trying to fit them in
-mid-way through.  Newer versions of the plugin should also be able to
-deal with changes to *old* ChangeLog entries, that should not be
-floated to the head of the file (see launchpad#723968).
-
-It is included in bzr from 2.4.0 onwards, so remember to delete the
-copy in ~/.bazaar if you upgrade bzr.
-
-Maybe the default Emacs behavior without this plugin is better,
-though, it's not clear yet.
-
-1) Get clean, up-to-date copies of the emacs-23 and trunk branches.
-Check for any uncommitted changes with bzr status.
-
-2) M-x cd /path/to/trunk
-
-The first time only, do this:
-cd .bzr/branch
-Add the following line to branch.conf:
-changelog_merge_files = ChangeLog
-
-3) load admin/bzrmerge.el
-
-4) M-x bzrmerge RET /path/to/emacs-23 RET
-
-It will prompt about revisions that should be skipped, based on the
-regexp in bzrmerge-missing.  If there are more revisions that you know
-need skipping, you'll have to do that by hand.
-
-5) It will stop if there are any conflicts.  Resolve them.
-Using smerge-mode, there are menu items to skip to the next conflict,
-and to take either the trunk, branch, or both copies.
-
-6) After resolving all conflicts, you might need to run the bzmerge
-command again if there are more revisions still to merge.
-
-Do not commit (or exit Emacs) until you have run bzrmerge to completion.
-
-Before committing, check bzr status and bzr diff output.
-If you have run bzrmerge enough times, the "pending merge tip" in bzr
-status should be the last revision from the emacs-23 branch, and
-bzr status -v should show all the revisions you expect to merge.
-
-(Note that it will also show "skipped" revisions.  This is expected,
-and is due to a technical limitation of bzr.  The log data for those
-revisions gets merged, the actual changes themselves do not.
-http://lists.gnu.org/archive/html/emacs-devel/2011-01/msg00609.html )
-
-In particular, check the ChangeLog entries (eg in case too many
-entries have been included or whitespace between entries needs fixing).
-bzrmerge tries to fix up the dates to today's date, but it only does
-this where there are conflicts.  If you used the changelog_merge plugin,
-there won't be any conflicts, and (at time of writing) you will need
-to adjust dates by hand.  In any case, if someone made multiple
-ChangeLog entries on different days in the branch, you may wish to
-collapse them all to a single entry for that author in the trunk
-(because in the trunk they all appear under the same date).
-Obviously, if there are multiple changes to the same file by different
-authors, don't break the logical ordering in doing this.
-
-Notes:
-
-1) A lot that was in tramp.el in emacs-23 has moved to tramp-sh.el in
-the trunk.  If you end up with a conflict in tramp.el, the changes may
-need to go to tramp-sh.el instead.  Remember to update the file name in
-the ChangeLog.
-
-2) If a file is modified in emacs-23, and deleted in the trunk, you
-get a "contents conflict".  Assuming the changes don't need to be in
-the trunk at all, use `bzr resolve path/to/file --take-this' to keep the
-trunk version.  Prior to bzr 2.2.3, this may fail.  You can just
-delete the .OTHER etc files by hand and use bzr resolve path/to/file.
-
-3) Conflicts in autoload md5sums in comments.  Strictly speaking, the
-right thing to do is merge everything else, resolve the conflict by
-choosing either the trunk or branch version, then run `make -C lisp
-autoloads' to update the md5sums to the correct trunk value before
-committing.
-
-* Re-adding a file that has been removed from the repository
-
-It's easy to get this wrong. Let's suppose you've done:
-
-bzr remove file; bzr commit
-
-and now, sometime later, you realize this was a mistake and file needs
-to be brought back.  DON'T just do:
-
-bzr add file; bzr commit
-
-This restores file, but without its history (`bzr log file' will be
-very short).  This is because file gets re-added with a new file-id
-(use `bzr file-id file' to see the id).
-
-Instead of adding the file, try:
-
-bzr revert -rN file; bzr commit
-
-where revision N+1 is the one where file was removed.
-
-You could also try `bzr add --file-ids-from', if you have a copy of
-another branch where file still exists.
-
-* Undoing a commit (uncommitting)
-
-It is possible to undo/remove a bzr commit (ie, to uncommit).
-Only do this if you really, really, need to.  For example, if you
-somehow made a commit that triggers a bug in bzr itself.
-Don't do it because you made a typo in a commit or the log.
-
-If you do need to do this, do it as soon as possible, because the
-longer you leave it, the more work is involved.
-
-0. First, tell emacs-devel that you are going to do this, and suggest
-people not commit anything to the affected branch for the duration.
-
-In the following, replace USER with your Savannah username, and
-BRANCH with the name of the branch.
-Let's assume that revno 100 is the bad commit, and that there have
-been two more commits after that (because nothing is ever easy).
-
-1. Ensure your copy of the branch is up-to-date (for a bound
-branch, bzr up; for an unbound branch, bzr pull) and has no local
-changes (bzr st).
-
-2. Make a record of the commits you are going to undo:
-bzr diff -c 102 > /tmp/102.diff
-etc
-
-Also record the commit message, author, and any --fixes information.
-
-3. Most Emacs branches are set up to prevent just this kind of thing.
-So we need to disable that protection:
-
-bzr config append_revisions_only=False \
-  -d bzr+ssh://USER@bzr.savannah.gnu.org/emacs/BRANCH/
-
-4. Undo the commits:
-bzr uncommit -r -4
-
-This will show the commits it is going to undo, and prompt you to confirm.
-
-5. If using an unbound branch:
-bzr push --overwrite
-
-6. Now, replay the commits you just undid (obviously, fix whatever it
-was in the bad commit that caused the problem):
-
-patch -p0 < /tmp/100.diff
-bzr commit --author ... --fixes ... -F /tmp/100.log
-etc
-
-7. If using an unbound branch:
-bzr push
-
-8. Finally, re-enable the branch protection:
-bzr config append_revisions_only=True \
-  -d bzr+ssh://USER@bzr.savannah.gnu.org/emacs/BRANCH/
-
-9. Tell emacs-devel that it is ok to use the branch again.
-Anyone with local changes should back them up before doing anything.
-
-For a bound branch, bzr up will convert any of the undone commits to a
-pending merge. Just bzr revert these away.
-
-For an unbound branch, bzr pull will complain about diverged branches
-and refuse to do anything.  Use bzr pull --overwrite.
-
-* Loggerhead
-
-Loggerhead is the bzr tool for viewing a repository over http (similar
-to ViewVC).  The central version is at http://bzr.savannah.gnu.org/lh/emacs,
-but if you just like the way this interface presents data, then if
-you have your own copy of the repository, you can operate your own
-Loggerhead server in stand-alone mode, and so help to reduce the load
-on Savannah:
-
-  bzr branch lp:loggerhead ~/.bazaar/plugins/loggerhead
-  cd /path/to/emacs/bzr
-  bzr serve --http
-
-You may need to install some Python dependencies to get this command to work.
-For example, on RHEL6 I needed:
-
-  yum install python-paste python-simplejson
-  yum --enablerepo=epel install python-simpletal
-
-Then point your web-browser to http://127.0.0.1:8080/ .
-
-* Bisecting
-
-This is a semi-automated way to find the revision that introduced a bug.
-
-First, get the bzr bisect plugin if you do not have it already:
-
-  cd ~/.bazaar/plugins
-  bzr branch lp:bzr-bisect bisect
-
-`bzr help bisect' should work now.
-
-It's probably simplest to make a new copy of the branch to work in
-from this point onwards.
-
-Identify the last known "good" revision where the relevant issue is
-NOT present (e.g. maybe Emacs 24.1).  Let's say this is revision 1000.
-
-  bzr bisect start
-  bzr bisect no -r 1000
-
-At this point, bzr will switch to the mid-point of revision 1000 and
-the current revision.  If you know that the issue was definitely
-present in some specific revision (say 2000), you can use:
-
-  bzr bisect yes -r 2000
-
-Now bzr switches to revision 1500.
-
-Now test whether the issue is present.  You might need to rebuild
-Emacs to do this, or if you know the problem is in a specific Lisp
-file, you might be able to get away with just loading that one file in
-current Emacs.
-
-If the issue is present, use
-
-  bzr bisect yes
-
-If it is not, use
-
-  bzr bisect no
-
-Repeat until you zero-in on the specific revision.
-
-When finished, use
-
-  bzr bisect reset
-
-or simply delete the entire branch if you created it just for this.
-
-* Commit emails
-
-** Old method: bzr-hookless-email
-https://launchpad.net/bzr-hookless-email
-
-Runs hourly via cron.  Must ask Savannah admins to enable/disable it
-for each branch.  Stores the last revision that it mailed as
-last_revision_mailed in branch.conf on the server.  Breaks with bzr 2.6:
-
-http://lists.gnu.org/archive/html/savannah-hackers-public/2013-05/msg00000.html
-
-Fix from https://bugs.launchpad.net/bzr-hookless-email/+bug/988195
-only partially works.  Breaks again on every merge commit:
-
-https://lists.ubuntu.com/archives/bazaar/2013q2/075520.html
-http://lists.gnu.org/archive/html/savannah-hackers-public/2013-05/msg00024.html
-
-You can force it to skip the merge commit by changing the value for
-last_revision_mailed, eg:
-
-bzr config last_revision_mailed=xfq.free@gmail.com-20130603233720-u1aumaxvf3o0rlai -d bzr+ssh://USERNAME@bzr.savannah.gnu.org/emacs/trunk/
-
-** New method: bzr-email plugin
-https://launchpad.net/bzr-email
-http://lists.gnu.org/archive/html/savannah-hackers-public/2013-06/msg00007.html
-
-Runs on commit.  Projects can enable it themselves by using `bzr
-config' to set post_commit_to option for a branch.  See `bzr help email'
-(if you have the plugin installed) for other options.
-
-Note: if you have the bzr-email plugin installed locally, then when
-you commit to the Emacs repository it will also try to send a commit
-email from your local machine.  If your machine is not configured to
-send external mail, this will just fail.  In any case, you may prefer
-to either remove the plugin from your machine, or disable it for Emacs
-branches.  You can do this either by editing branch.conf in your Emacs
-branches, to override the server setting (untested; not sure this
-works), or by adding an entry to ~/.bazaar/locations.conf:
-
-  [bzr+ssh://USERNAME@bzr.savannah.gnu.org/emacs/*/]
-  post_commit_to = ""
-
-You have to use locations.conf rather than bazaar.conf because the
-latter has a lower priority than branch.conf.
diff --git a/admin/notes/changelogs b/admin/notes/changelogs
deleted file mode 100644
index 1025cfc217f..00000000000
--- a/admin/notes/changelogs
+++ /dev/null
@@ -1,23 +0,0 @@
-If installing changes written by someone else, make the ChangeLog
-entry in their name, not yours.
-
-
-http://lists.gnu.org/archive/html/emacs-devel/2007-09/msg00793.html
-  There is no need to make change log entries for files such as NEWS,
-  MAINTAINERS, and FOR-RELEASE.
-"There is no need" means you don't have to, but you can if you want to.
-
-
-http://lists.gnu.org/archive/html/emacs-devel/2006-12/msg01135.html
-  There is no need to indicate regeneration of files such as configure
-  in ChangeLog.
-
-
-http://lists.gnu.org/archive/html/emacs-devel/2008-11/msg00940.html
-Preferred form for several entries with the same content:
-
-   * help.el (view-lossage):
-   * kmacro.el (kmacro-edit-lossage):
-   * edmacro.el (edit-kbd-macro): Fix docstring, lossage is now 300 keys.
-
-(Rather than anything involving "ditto" and suchlike.)
diff --git a/admin/notes/commits b/admin/notes/commits
deleted file mode 100644
index 2c6f80c56f0..00000000000
--- a/admin/notes/commits
+++ /dev/null
@@ -1,61 +0,0 @@
-HOW TO COMMIT CHANGES TO EMACS
-
-Most of these points are from:
-
-http://lists.gnu.org/archive/html/emacs-devel/2009-03/msg00555.html
-From:    Miles Bader
-Subject: commit style redux
-Date:    Tue, 31 Mar 2009 12:21:20 +0900
-
-(0) Each commit should correspond to a single change (whether spread
-    over multiple files or not).  Do not mix different changes in the
-    same commit (eg adding a feature in one file, fixing a bug in
-    another should be two commits, not one).
-
-(1) Commit all changed files at once with a single log message (which
-    in CVS will result in an identical log message for all committed
-    files), not one-by-one.  This is pretty easy using vc-dir now.
-
-(2) Make the log message describe the entire changeset, perhaps
-    including relevant changelog entries (I often don't bother with
-    the latter if it's a trivial sort of change).
-
-    Many modern source-control systems vaguely distinguish the first
-    line of the log message to use as a short summary for abbreviated
-    history listing (in arch this was explicitly called the summary,
-    but many other systems have a similar concept).  So it's nice if
-    you can format the log entry like:
-
-        SHORTISH ONE-LINE SUMMARY
-
-        MULTIPLE-LINE DETAILED DESCRIPTION POSSIBLY INCLUDING (OR
-        CONSISTING OF) CHANGELOG ENTRIES
-
-    [Even with CVS this style is useful, because web CVS browsing
-    interfaces often include the first N words of the log message of
-    the most recent commit as a short "most recent change"
-    description.]
-
-(3) Don't phrase log messages assuming the filename is known, because
-    in non-file-oriented systems (everything modern other than CVS),
-    the log listing tends to be treated as global information, and the
-    connection with specific files is less explicit.
-
-    For instance, currently I often see log messages like "Regenerate";
-    for modern source-control systems with a global log, it's better to
-    have something like "Regenerate configure".
-
-
-Followup discussion:
-http://lists.gnu.org/archive/html/emacs-devel/2010-01/msg00897.html
-http://lists.gnu.org/archive/html/emacs-devel/2010-02/msg00401.html
-
-
-PREVIOUS GUIDELINES FOR CVS
-
-For historical interest only, here is the old-style advice for CVS logs:
-http://lists.gnu.org/archive/html/emacs-devel/2007-12/msg01208.html
-
-From: Eli Zaretskii
-Subject: Re: Log messages in CVS
-Date: Sat, 29 Dec 2007 16:06:29 +0200
diff --git a/admin/notes/copyright b/admin/notes/copyright
index 3a404b69678..3ba9c55d246 100644
--- a/admin/notes/copyright
+++ b/admin/notes/copyright
@@ -1,4 +1,4 @@
-Copyright (C) 2007-2013 Free Software Foundation, Inc.
+Copyright (C) 2007-2015 Free Software Foundation, Inc.
 See the end of the file for license conditions.
 
 
@@ -22,9 +22,9 @@ author to make a non-trivial total. If so, make sure they have an
 assignment. If adding a whole file adjust the copyright statements in
 the file.
 
-2. When installing code written by someone else, the ChangeLog entry
+2. When installing code written by someone else, the commit
 should be in the name of the author of the code, not the person who
-installs it.  Also use bzr commit's "--author" option.
+installs it.  Also use commit's "--author" option.
 Do not install any of your own changes in the same commit.
 
 3. With images, add the legal info to a README file in the directory
@@ -115,8 +115,8 @@ else it is possible the file should not be in Emacs at all (please
 report!).
 
 Note that it seems painfully clear that one cannot rely on commit logs,
-or even ChangeLogs, for older changes. People often installed changes
-from others, without recording the true authorship.
+or even change log entries, for older changes. People often installed
+changes from others, without recording the true authorship.
 
 [For reference, most of these points were established via email with
 rms, 2007/1, "Copyright years".
@@ -132,12 +132,15 @@ lib-src/rcs2log           # Copyright
 Cocoa/Emacs.base/Contents/Info.plist
 Cocoa/Emacs.base/Contents/Resources/English.lproj/InfoPlist.strings
 GNUstep/Emacs.base/Resources/Info-gnustep.plist
-   `set-copyright' in admin.el will do all the above.
+   'set-copyright' in admin.el will do all the above.
 
 aclocal.m4
 configure
 m4/*.m4
- - copyright FSF, with unlimited permission to copy, distribute and modify
+ - These files are copyright FSF, with unlimited permission to copy,
+   distribute and modify, so long as the copyright notice is preserved.
+   Exception: m4/pkg.m4 is copyright Scott James Remnant; it is
+   distributed under the same terms as for the rest of Emacs.
 
 lib/Makefile.in
  - copyright FSF, with MIT-like license
@@ -161,13 +164,6 @@ etc/letter.pbm,letter.xpm
 etc/FTP, ORDERS
   - trivial (at time of writing), no license needed
 
-etc/GNU, INTERVIEW, LINUX-GNU, MOTIVATION, SERVICE, THE-GNU-PROJECT,
-WHY-FREE
-  rms: "These are statements of opinion or testimony. Their licenses
-  should permit verbatim copying only. Please don't change the
-  licenses that they have. They are distributed with Emacs but they
-  are not part of Emacs."
-
 etc/HELLO
   standard notices. Just a note that although the file itself is not
   really copyrightable, in the wider context of it being part of
@@ -320,11 +316,6 @@ licensing@fsf.org starting on Thu, 07 Aug 2003 with subject:
 "[gnu.org #58812] Changing license of MH-E manual"
 
 
-msdos/is_exec.c, sigaction.c - these files are copyright DJ Delorie.
-Leave the copyrights alone. Leave the Eli Zaretskii copyright in
-is_exec.c alone. See the msdos/README file for the legal history of
-these files.
-
 msdos/sed*.inp - These files are copyright FSF and distributed under
 an MIT-like license.
 
@@ -493,10 +484,10 @@ system)
     obviously good):
 
 
-Is it OK to just `bzr remove' a file for legal reasons, or is
-something more drastic needed? A removed file is still available from
-the repository, if suitable options are applied. (This issue obviously
-does not affect a release).
+Is it OK to just remove a file for legal reasons, or is something more
+drastic (excision from the entire repository history) needed? A
+removed file is still available from the repository, if suitable
+options are applied. (This issue obviously does not affect a release).
   rms: will ask lawyer
 
 
@@ -567,8 +558,7 @@ oldXMenu/insque.c (rms: "We wrote that specifically for Emacs, so
 definitely relicense that.").
 
 2. The files that are copyright FSF and AIST, or AIST alone, should be
-and were updated, ditto the oldXMenu files with FSF copyright, and
-msdos/is_exec.c and sigaction.c.
+and were updated, ditto the oldXMenu files with FSF copyright.
 
 3. lwlib/
 
diff --git a/admin/notes/elpa b/admin/notes/elpa
index db14456fe32..4c0f1980def 100644
--- a/admin/notes/elpa
+++ b/admin/notes/elpa
@@ -1,24 +1,21 @@
 NOTES ON THE EMACS PACKAGE ARCHIVE
 
-The GNU Emacs package archive, at elpa.gnu.org, is managed using a Bzr
-branch named "elpa", hosted on Savannah.  To check it out:
+The GNU Emacs package archive, at elpa.gnu.org, is managed using a Git
+repository named "elpa", hosted on Savannah.  To check it out:
 
-  bzr branch bzr+ssh://USER@bzr.savannah.gnu.org/emacs/elpa elpa
+  git clone git://git.sv.gnu.org/emacs/elpa
   cd elpa
-  echo "public_branch = bzr+ssh://USER@bzr.savannah.gnu.org/emacs/elpa" >> .bzr/branch/branch.conf
-  bzr bind bzr+ssh://USERNAME@bzr.savannah.gnu.org/emacs/elpa
+  git remote set-url --push origin git+ssh://git.sv.gnu.org/srv/git/emacs/elpa
   [create task branch for edits, etc.]
 
-Changes to this branch propagate to elpa.gnu.org in a semi-manual way.
-There exists a copy of the elpa branch on that machine.  Someone with
-access logs in, pulls the latest changes from Savannah, and runs a
-"deployment" script.  This script (which is itself kept in the Bzr
-branch) generates the content visible at http://elpa.gnu.org/packages.
+Changes to this branch propagate to elpa.gnu.org via a "deployment" script run
+daily.  This script (which is kept in elpa/admin/update-archive.sh) generates
+the content visible at http://elpa.gnu.org/packages.
 
-The reason we set things up this way, instead of using the package
-upload commands in package-x.el, is to let Emacs hackers conveniently
-edit the contents of the "elpa" branch.  (In particular, multi-file
-packages are stored on the branch in source form, not as tarfiles.)
+A new package is released as soon as the "version number" of that package is
+changed.  So you can use 'elpa' to work on a package without fear of releasing
+those changes prematurely.  And once the code is ready, just bump the
+version number to make a new release of the package.
 
 It is easy to use the elpa branch to deploy a "local" copy of the
 package archive.  For details, see the README file in the elpa branch.
diff --git a/admin/notes/exit-value b/admin/notes/exit-value
deleted file mode 100644
index cad6862c8aa..00000000000
--- a/admin/notes/exit-value
+++ /dev/null
@@ -1,35 +0,0 @@
-ttn 2004-05-09
-
-The exit value of a program returning to the shell on unixoid systems is
-typically 0 for success, and non-0 (such as 1) for failure.  For vms it is
-odd (1,3,5...) for success, even (0,2,4...) for failure.
-
-This holds from the point of view of the "shell" (in quotes because vms has a
-different dispatch model that is not explained further here).
-
-From the point of view of the program, nowadays stdlib.h on both type of
-systems provides macros `EXIT_SUCCESS' and `EXIT_FAILURE' that should DTRT.
-
-NB: The numerical values of these macros DO NOT need to fulfill the exit
-value requirements outlined in the first paragraph!  That is the job of the
-`exit' function.  Thus, this kind of construct shows misunderstanding:
-
-   #ifdef VMS
-      exit (1);
-   #else
-      exit (0);
-   #endif
-
-Values aside from EXIT_SUCCESS and EXIT_FAILURE are tricky.
-
-
-
-ttn 2004-05-12
-
-Values aside from EXIT_SUCCESS and EXIT_FAILURE can be used to indicate
-finer gradations of failure.  If this is the only information available
-to the caller, clamping such values to EXIT_FAILURE loses information.
-If there are other ways to indicate the problem to the caller (such as
-a message to stderr) it may be ok to clamp.  In all cases, it is the
-relationship between the program and its caller that must be examined.
-[Insert ZAMM quote here.]
diff --git a/admin/notes/font-backend b/admin/notes/font-backend
index cdf2001580d..03663d38cd8 100644
--- a/admin/notes/font-backend
+++ b/admin/notes/font-backend
@@ -1,4 +1,4 @@
-Copyright (C) 2002-2013 Free Software Foundation, Inc.
+Copyright (C) 2002-2015 Free Software Foundation, Inc.
 See the end of the file for license conditions.
 
 
diff --git a/admin/notes/git-workflow b/admin/notes/git-workflow
new file mode 100644
index 00000000000..3c2c76c8909
--- /dev/null
+++ b/admin/notes/git-workflow
@@ -0,0 +1,143 @@
+(This is a draft.  The method here won't actually work yet, because
+neither git-new-workdir nor merge-changelog are in the Emacs
+distribution yet.)
+
+Setting up and using git for normal, simple bugfixing
+=====================================================
+
+If you haven't configured git before you should first do:
+
+git config --global user.name "Frank Chu"
+git config --global user.email "fchu@example.com"
+
+Initial setup
+=============
+
+Then we want to clone the repository.  We normally want to have both
+the current trunk and the emacs-24 branch.
+
+mkdir ~/emacs
+cd ~/emacs
+git clone <membername>@git.sv.gnu.org:/srv/git/emacs.git
+mv emacs trunk
+(cd trunk; git config push.default current)
+./trunk/admin/git-new-workdir trunk emacs-24
+cd emacs-24
+git checkout emacs-24
+git config push.default current
+
+You now have both branches conveniently accessible, and you can do
+"git pull" in them once in a while to keep updated.
+
+
+Fixing bugs
+===========
+
+You edit the files in either branch, 'M-x vc-dir', and check in your
+changes.  Then you need to push the data to the main repository.  This
+will usually fail, since somebody else has pushed other changes in the
+meantime.  To fix this, say
+
+git pull --rebase
+
+which will update your repository, and then re-apply your changes on
+top of that.  Then say
+
+git push
+
+
+Sending patches
+===============
+
+If you lack push access or would like feedback before pushing a patch,
+you commit your change locally and then send a patch file as a bug report
+as described in ../../CONTRIBUTE.
+
+
+Backporting to emacs-24
+=======================
+
+If you have applied a fix to the trunk, but then decide that it should
+be applied to the emacs-24 branch, too, then
+
+cd ~/emacs/trunk
+git log
+
+and find the commit you're looking for.  Then find the commit ID,
+which will look like
+
+commit 958b768a6534ae6e77a8547a56fc31b46b63710b
+
+cd ~/emacs/emacs-24
+git cherry-pick -xe 958b768a6534ae6e77a8547a56fc31b46b63710b
+
+and add "Backport:" to the commit string.  Then
+
+git push
+
+
+Merging emacs-24 to trunk/master
+================================
+
+It is recommended to use the file gitmerge.el in the admin directory
+for merging 'emacs-24' into 'master'.  It will take care of many
+things which would otherwise have to be done manually, like ignoring
+commits that should not land in master, fixing up ChangeLogs and
+automatically dealing with certain types of conflicts.  If you really
+want to, you can do the merge manually, but then you're on your own.
+If you still choose to do that, make absolutely sure that you *always*
+use the 'merge' command to transport commits from 'emacs-24' to
+'master'.  *Never* use 'cherry-pick'!  If you don't know why, then you
+shouldn't manually do the merge in the first place; just use
+gitmerge.el instead.
+
+How to use gitmerge.el:
+
+Enter the Emacs repository, checkout 'master' and make sure it's
+up-to-date by doing a pull.  Then start Emacs with
+
+  emacs -l admin/gitmerge.el -f gitmerge
+
+You'll be asked for the branch to merge, which will default to
+'origin/emacs-24', which you should accept.  Merging a local tracking
+branch is discouraged, since it might not be up-to-date, or worse,
+contain commits from you which are not yet pushed upstream.
+
+You will now see the list of commits from 'emacs-24' which are not yet
+merged to 'master'.  You might also see commits that are already
+marked for "skipping", which means that they will be merged with a
+different merge strategy ('ours'), which will effectively ignore the
+commit's diff while still being seen as merged, so it won't turn up
+again in future merges.  Recognizing these kinds of commits is done
+with a simple regexp searching the log for strings like 'backport' or
+'merge', so you'll probably see false positives as well as false
+negatives.  Carefully go through the commits, investigate them by
+hitting 'l', 'd' and 'f', and mark or unmark them for skipping with
+'s'.  When you're done, hit 'm' to start the merge.
+
+You'll likely get conflicts during the process which cannot be dealt
+with automatically.  In that case, the merge will stop and show you
+the list of conflicted files.  Resolve those conflicts as usual using
+smerge and restart gitmerge (remember to enter the repository when
+doing that).  You don't have to 'add' the resolved files and 'commit'
+the resulting merge, but if you really want to, feel free to do that.
+Note you can also resume gitmerge in a new Emacs session, since the
+current state will be saved to disk.
+
+When everything's done, look hard at the resulting merge.  Skipping
+commits requires separate merges, so don't be surprised to see more
+than one merge commit.  If you're happy, push.
+
+Warnings about X11 forwarding
+=============================
+
+If you get warnings like
+
+Warning: No xauth data; using fake authentication data for X11 forwarding.
+X11 forwarding request failed on channel 0
+
+when pulling or pushing data, add the following to the start of
+~/.ssh/config:
+
+Host git.sv.gnu.org
+   ForwardX11 no
diff --git a/admin/notes/hydra b/admin/notes/hydra
index 068bc70ee9c..ce4a683f6fe 100644
--- a/admin/notes/hydra
+++ b/admin/notes/hydra
@@ -1,24 +1,23 @@
--*- outline -*-
+-*- mode: outline; coding: utf-8 -*-
 
-Copyright (C) 2013 Free Software Foundation, Inc.
+Copyright (C) 2013-2015 Free Software Foundation, Inc.
 See the end of the file for license conditions.
 
 NOTES FOR EMACS CONTINUOUS BUILD ON HYDRA
 
-A continuous build for Emacs trunk can be found at
+A continuous build for Emacs can be found at
 http://hydra.nixos.org/jobset/gnu/emacs-trunk
+http://hydra.nixos.org/jobset/gnu/emacs-24
 
-* It builds (and runs ERT tests) on these platforms:
-i686-cygwin
-i686-freebsd
-i686-linux
-x86_64-darwin
-x86_64-linux
+* It builds Emacs on various platforms.
+Sometimes jobs fail due to hydra problems rather than Emacs problems.
+Eg it seems like the cygwin build will never work again.
+http://lists.gnu.org/archive/html/hydra-users/2013-08/msg00000.html
 
 * Mail notifications
 In addition to the web interface, Hydra can send notifications by
-email when the build status of a project changes—e.g., from
-`SUCCEEDED' to `FAILED'.  It sends notifications about build status in
+email when the build status of a project changes, e.g., from
+SUCCEEDED to FAILED.  It sends notifications about build status in
 Emacs trunk to emacs-buildstatus@gnu.org.
 
 If you want to receive these notifications, please subscribe at
@@ -26,16 +25,16 @@ http://lists.gnu.org/mailman/listinfo/emacs-buildstatus
 
 * The Emacs jobset consists of the following jobs:
 
-** The `tarball' job
-which gets the source tree as input, and is just a `make dist' after
-some autoconf/-make or bootstrap script.
+** The 'tarball' job
+which gets a checkout from the repository, and does a bootstrap followed
+by running make-dist to create a tarball.  If this job fails, all the
+others will too (because they use the tarball as input).
 
-** The `build' job
-which gets the result of the tarball job as input, together with
-system identifier, this job basically does a normal make and make install.
+** The 'build' job
+which starts from the tarball and does a normal build
 
 ** The 'coverage' job
-is now running `make check'.
+does a gcov build and then runs 'make check'.  Fails if any test fails.
 
 * Nix expressions
 The recipe for GNU Emacs are available via Git:
diff --git a/admin/notes/iftc b/admin/notes/iftc
deleted file mode 100644
index 983b1486685..00000000000
--- a/admin/notes/iftc
+++ /dev/null
@@ -1,26 +0,0 @@
-Iso-Functional Type Contour
-
-
-This is a term coined to describe "column int->float" change approach, and can
-be used whenever low-level types need to change (hopefully not often!) but the
-meanings of the values (whose type has changed) do not.
-
-The premise is that changing a low-level type potentially means lots of code
-needs to be changed as well, and the question is how to do this incrementally,
-which is the preferred way to change things.
-
-Say LOW and HIGH are C functions:
-
-  int LOW (void) { return 1; }
-  void HIGH (void) { int value = LOW (); }
-
-We want to convert LOW to return float, so we cast HIGH usage:
-
-  float LOW (void) { return 1.0; }
-  void HIGH (void) { int value = (int) LOW (); }  /* iftc */
-
-The comment /* iftc */ is used to mark this type of casting to differentiate
-it from other casting.  We commit the changes and can now go about modifying
-LOW and HIGH separately.  When HIGH is ready to handle the type change, the
-cast can be removed.
-
diff --git a/admin/notes/lel-TODO b/admin/notes/lel-TODO
deleted file mode 100644
index 2c6d86a4ffd..00000000000
--- a/admin/notes/lel-TODO
+++ /dev/null
@@ -1,124 +0,0 @@
-Some lisp/emacs-lisp/ Features and Where They Are Documented
-
-Copyright (C) 2007-2013 Free Software Foundation, Inc.
-See the end of the file for license conditions.
-
-
-* Status Key
-  -      -- as yet unknown
-  n/a    -- not applicable (internal, uninteresting, etc)
-  obsolete -- an obsolete feature, to be removed in future
-  todo   -- not documented but should be
-  NODE   -- documented in or under info node NODE
-
-
-* Features
-  advice                  (elisp) Advising Functions
-  advice-preload          n/a
-  assoc                   -
-  authors                 -
-  autoload                (elisp) Autoload
-  avl-tree                -
-  backquote               n/a
-  benchmark               n/a
-  bindat                  (elisp) Byte Packing
-  byte-compile            (elisp) Byte Compilation
-  byte-opt                -
-  bytecomp                (elisp) Compilation Functions
-  checkdoc                (elisp) Documentation Tips
-  cl                      (cl)
-  cl-compat               n/a
-  cl-specs                n/a
-  copyright               -
-  crm                     -
-  cust-print              (elisp) Printing in Edebug
-  debug                   (elisp) Debugger
-  derived                 (elisp) Derived Modes
-  disass                  (elisp) Disassembly
-  easy-mmode              (elisp) Defining Minor Modes
-  easymenu                -
-  edebug                  (elisp) Edebug
-  eldoc                   -
-  elint                   -
-  elp                     n/a
-  ewoc                    (elisp) Separated Rendering
-  find-func               -
-  find-gc                 -
-  generic                 (elisp) Generic Modes
-  gulp                    n/a
-  helper                  -
-  levents                 obsolete
-  lisp-float-type         -
-  lisp-mnt                -
-  lisp-mode               n/a
-  lmenu                   obsolete
-  lucid                   obsolete
-  macroexp                (elisp) Expansion
-  pp                      (emacs) Program Indent
-  re-builder              -
-  regexp-opt              (elisp) Regexp Functions
-  regi                    -
-  ring                    (elisp) Rings
-  rx                      -
-  shadow                  -
-  sregex                  obsolete
-  syntax                  (elisp) Position Parse
-  testcover               -
-  timer                   (elisp) Timers
-  tq                      (elisp) Transaction Queues
-  trace                   -
-  unsafep                 (elisp) Function Safety
-  warnings                (elisp) Warnings
-
-
-* Above list created using default directory lisp/emacs-lisp/ with
-  (shell-command
-    "sed '/^(provide '\\''/!d;s//  /;s/).*//' *.el | sort | uniq")
-
-
-* How to use this file to improve Emacs
-  (loop
-   (let* ((feature (choose-one Features))
-          (status (feature-status feature)))
-     (if (or (eq '- status) (not (verify status)))
-         (update feature (current-docs feature))
-       (case status
-         (todo (let (doc patch feedback)
-                 (while (not (grok feature))
-                   (or (play-with feature)
-                       (grep feature Internet)
-                       (grep feature (wisdom-maybe "emacs-devel"))))
-                 (setq doc (write-documentation feature)
-                       patch (diff (current-docs) doc))
-                 (while (not (and (correct doc)
-                                  (well-placed doc)
-                                  (well-formed patch)))
-                   (setq doc (revise doc)
-                         patch (diff (current-docs) doc))
-                         feedback (wisdom-maybe "emacs-devel" patch))
-                 (when (install patch)
-                   (when (update feature (current-docs feature))
-                     (job-well-done user-login-name)))))
-         (n/a (job-well-done user-login-name))))))
-
-
-* Etc
-
-This file is part of GNU Emacs.
-
-GNU Emacs is free software: you can redistribute it and/or modify
-it under the terms of the GNU General Public License as published by
-the Free Software Foundation, either version 3 of the License, or
-(at your option) any later version.
-
-GNU Emacs is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-GNU General Public License for more details.
-
-You should have received a copy of the GNU General Public License
-along with GNU Emacs.  If not, see <http://www.gnu.org/licenses/>.
-
-  Local variables:
-  mode: outline
-  End:
diff --git a/admin/notes/multi-tty b/admin/notes/multi-tty
index c4edd3abc93..868d45138d8 100644
--- a/admin/notes/multi-tty
+++ b/admin/notes/multi-tty
@@ -1,6 +1,6 @@
 -*- coding: utf-8; mode: text; -*-
 
-Copyright (C) 2007-2013 Free Software Foundation, Inc.
+Copyright (C) 2007-2015 Free Software Foundation, Inc.
 See the end of the file for license conditions.
 
 From README.multi-tty in the multi-tty branch.
@@ -82,7 +82,7 @@ Known problems:
           minibuffer prompt (which is a kind of recursive editing) on
           another display.  To unfreeze your session, switch to that
           display and complete the recursive edit, for example by
-          pressing C-] (`abort-recursive-edit').
+          pressing C-] ('abort-recursive-edit').
 
           I am sorry to say that currently there is no way to break
           out of this "single-kboard mode" from a frozen display.  If
@@ -101,16 +101,6 @@ Known problems:
           I plan to implement better user notification and support for
           breaking out of single-kboard mode from locked displays.
 
-        * Mac and DOS support is broken, doesn't even
-          compile.  Multiple display support will probably not provide
-          new Emacs features on these systems, but the multi-tty
-          branch changed a few low-level interfaces, and the
-          system-dependent source files need to be adapted
-          accordingly.  The changes are mostly trivial, so almost
-          anyone can help, if only by compiling the branch and
-          reporting the compiler errors.
-
-
 TESTING
 -------
 
@@ -219,11 +209,11 @@ following:
 THINGS TO DO
 ------------
 
-** See if `tty-defined-color-alist' needs to be terminal-local.
+** See if 'tty-defined-color-alist' needs to be terminal-local.
    Update: Dan says it should be, so convert it.
 
 ** Mikhail Gusarov suggest to add a hook akin to
-   `after-make-frame-functions' that is called whenever Emacs connects
+   'after-make-frame-functions' that is called whenever Emacs connects
    to a new terminal.  Good idea!
 
 ** emacsclient -t on the console does not work after su.  You have to
@@ -247,16 +237,16 @@ THINGS TO DO
    proxy idea.
 
 ** lisp/vc.el depends on the terminal type during load time.
-   `vc-annotate-color-map' is one example that needs to be fixed.
+   'vc-annotate-color-map' is one example that needs to be fixed.
 
-** Understand how `quit_throw_to_read_char' works, and fix any bugs
+** Understand how 'quit_throw_to_read_char' works, and fix any bugs
    that come to light.
 
 ** See if getcjmp can be eliminated somehow.  Why does Emacs allow
    asynchronous input processing while it's reading input anyway?
 
-** `delete-frame' events are handled by `special-event-map'
-   immediately when read by `read_char'.  This is fine but it prevents
+** 'delete-frame' events are handled by 'special-event-map'
+   immediately when read by 'read_char'.  This is fine but it prevents
    higher-level keymaps from binding that event to get notified of the
    deleted frame.
 
@@ -264,26 +254,26 @@ THINGS TO DO
    deletions after they have happened, usually because they want to
    clean up after the deleted frame.  Not all frame-local states can
    be stored as a frame parameter.  For example,
-   `display-splash-screen' uses `recursive-edit' with a special keymap
+   'display-splash-screen' uses 'recursive-edit' with a special keymap
    override to create its buffer---and it leads to all kinds of
    nastiness if Emacs stays in this recursive edit mode after the
    frame containing the splash screen is deleted.  Basically, the
    splash-screen implementation wants to throw out of the recursive
    edit when the frame is deleted; however, it is not legal to throw
-   from `delete-frame-functions' because `delete-frame' must not fail.
-   (Introducing `delete-frame-after-functions' would not help either
-   because `delete-frame' may not fail at that time either.)
+   from 'delete-frame-functions' because 'delete-frame' must not fail.
+   (Introducing 'delete-frame-after-functions' would not help either
+   because 'delete-frame' may not fail at that time either.)
 
-   Currently `fancy-splash-screens' installs a
-   `delete-frame-functions' hook that sets up a timer to exit the
+   Currently 'fancy-splash-screens' installs a
+   'delete-frame-functions' hook that sets up a timer to exit the
    recursive edit.  This is an adequate solution, but it would perhaps
-   be better to have something like a `frame-deleted' event that could
+   be better to have something like a 'frame-deleted' event that could
    be bound in the normal way.
 
-** Trouble: `setenv' doesn't actually set environment variables in the
+** Trouble: 'setenv' doesn't actually set environment variables in the
    Emacs process.  This defeats the purpose of the elaborate
-   `server-with-environment' magic around the `tgetent' call in
-   `init_tty'.  D'oh.
+   'server-with-environment' magic around the 'tgetent' call in
+   'init_tty'.  D'oh.
 
 ** (Possibly) create hooks in struct device for creating frames on a
    specific terminal, and eliminate the hackish terminal-related frame
@@ -300,9 +290,9 @@ THINGS TO DO
    as static, removing it from dispextern.h.
    Move fatal to emacs.c and declare it somewhere.
 
-** Search for `suspend-emacs' references and replace them with
-   `suspend-frame', if necessary.  Ditto for `save-buffers-kill-emacs'
-   vs. `save-buffers-kill-display'.
+** Search for 'suspend-emacs' references and replace them with
+   'suspend-frame', if necessary.  Ditto for 'save-buffers-kill-emacs'
+   vs. 'save-buffers-kill-display'.
 
 ** Emacs crashes when a tty frame is resized so that there is no space
    for all its windows.  (Tom Schutzer-Weissmann)
@@ -325,7 +315,7 @@ THINGS TO DO
    impression that the various multidisplay fixes will only get
    released in GTK+ 2.10.
 
-** Audit `face-valid-attribute-values' usage in customize and
+** Audit 'face-valid-attribute-values' usage in customize and
    elsewhere.  Its return value depends on the current window system.
    Replace static initializers using it with runtime functions.  For
    example, custom's buttons are broken on non-initial device types.
@@ -335,9 +325,9 @@ THINGS TO DO
 
 ** frames-on-display-list should also accept frames.
 
-** Consider the `tty-type' frame parameter and the `display-tty-type'
+** Consider the 'tty-type' frame parameter and the 'display-tty-type'
    function.  They serve the exact same purpose.  I think it may be
-   a good idea to eliminate one of them, preferably `tty-type'.
+   a good idea to eliminate one of them, preferably 'tty-type'.
 
 ** The handling of lisp/term/*.el, and frame creation in general, is a
    big, big mess.  How come the terminal-specific file is loaded by
@@ -350,27 +340,23 @@ THINGS TO DO
    changed in CVS, and frame.el in multi-tty has not yet been adapted
    for the changes.  (It needs to look at
    default-frame-background-mode.)  (Update: maybe it is fixed now;
-   needs testing.) (Note that the byte compiler has this to say about
-   term/rxvt.el:)
-
-        term/rxvt.el:309:17:Warning: assignment to free variable
-            `default-frame-background-mode'
+   needs testing.)
 
-** I think `(set-)terminal-local-value' and the terminal parameter
+** I think '(set-)terminal-local-value' and the terminal parameter
    mechanism should be integrated into a single framework.
 
-   (Update: `(set-)terminal-local-value' is now eliminated, but the
+   (Update: '(set-)terminal-local-value' is now eliminated, but the
    terminal-local variables should still be accessible as terminal
-   parameters.  This also applies to `display-name' and similar
+   parameters.  This also applies to 'display-name' and similar
    functions.)
 
 ** Add the following hooks: after-delete-frame-hook (for server.el,
    instead of delete-frame-functions),
    after-delete-terminal-functions, after-create-terminal-functions.
 
-** BULK RENAME: The `display-' prefix of new Lisp-level functions
-   conflicts with stuff like `display-time-mode'.  Use `device-'
-   or `terminal-' instead.  I think I prefer `terminal-'.
+** BULK RENAME: The 'display-' prefix of new Lisp-level functions
+   conflicts with stuff like 'display-time-mode'.  Use 'device-'
+   or 'terminal-' instead.  I think I prefer 'terminal-'.
 
    It turns out that most of the offending Lisp functions were defined
    in the trunk.  Therefore, compatibility aliases should be defined
@@ -476,7 +462,7 @@ THINGS TO DO
 
 ** With iswitchb-default-method set to 'always-frame, only frames on
    the current display should be considered.  This might involve
-   extending `get-buffer-window'.
+   extending 'get-buffer-window'.
 
 ** Have a look at Vlocale_coding_system.  Seems like it would be a
    tedious job to localize it, although most references use it for
@@ -504,17 +490,6 @@ THINGS TO DO
 
    (This is likely an error in the CVS trunk.)
 
-** Dan Nicolaescu suggests that -nw should be added as an alias for -t
-   in emacsclient.  Good idea.  (Alas, implementing this is not
-   trivial, getopt_long does not seem to support two-letter ``short''
-   options.  Patches are welcome.)
-
-** Mark Plaksin suggests that emacsclient should accept the same
-   X-related command-line arguments as Emacs.  Most of the X-related
-   argument-handling is done in Lisp, so this should be quite easy to
-   implement.  (For example, Samium Gromoff wants emacsclient to
-   support --geometry; implementing this would add that support.)
-
 ** Gergely Nagy suggests that C-x # should only kill the current
    frame, not any other emacsclient frame that may have the same file
    opened for editing.  I think I agree with him.
@@ -532,21 +507,9 @@ THINGS TO DO
    an initial frame.  (The user would connect to it and open frames
    later, with emacsclient.)
 
-** Fix Mac support (I can't do this entirely myself).  Note that the
-   current state of Mac-specific source files in the multi-tty tree
-   are not useful; before starting work on Mac support, revert to
-   pristine, pre-multi-tty versions.
-
-** Fix DOS support (I can't do this entirely myself).  Note that the
-   current state of DOS-specific source files in the multi-tty tree
-   are not useful; before starting work on DOS support, revert to
-   pristine, pre-multi-tty versions.
-
-** Fix Windows support. Currently bootstrapping works on w32, but Emacs
-   crashes on startup and none of the multi-tty features are
-   implemented. Many XXX comments mark things that probably need
-   updating, ChangeLogs will help in spotting changes to X specific
-   files that may need porting.
+** Implement Mac/Windows/DOS support.  Many XXX comments mark things
+   that probably need updating, ChangeLogs will help in spotting
+   changes to X specific files that may need porting.
 
 ** Do a grep on XXX and ?? for more issues.
 
@@ -570,7 +533,7 @@ DIARY OF CHANGES
 
 -- Change make-terminal-frame to support specifying another tty.
 
-   (Done, new frame parameters: `tty' and `tty-type'.)
+   (Done, new frame parameters: 'tty' and 'tty-type'.)
 
 -- Implement support for reading from multiple terminals.
 
@@ -582,7 +545,7 @@ DIARY OF CHANGES
 
    (Update2: After enabling X, they don't.)
 
--- other-frame should cycle through the frames on the `current'
+-- other-frame should cycle through the frames on the 'current'
    terminal only.
 
    (Done, by trivially modifying next_frame and prev_frame.)
@@ -639,7 +602,7 @@ DIARY OF CHANGES
 
    (Update^3: Not any more.)
 
--- Make make-terminal-frame look up the `tty' and `tty-type' frame
+-- Make make-terminal-frame look up the 'tty' and 'tty-type' frame
    parameters from the currently selected terminal before the global
    default.
 
@@ -857,7 +820,7 @@ DIARY OF CHANGES
 
    (Done, breaking interactive temacs.)
 
--- The command `emacsclient -t -e '(delete-frame)'' fails to exit.
+-- The command "emacsclient -t -e '(delete-frame)'" fails to exit.
 
    (Fixed.)
 
@@ -967,7 +930,7 @@ DIARY OF CHANGES
    frame sets single_kboard).  Update: the face problems are caused by
    bugs in term.el, not in multi-tty.  The lockup is caused by
    single_kboard mode, and is not easily resolvable.  The best thing to
-   do is to simply refuse to create a tty frame of type `eterm'.
+   do is to simply refuse to create a tty frame of type 'eterm'.
 
    (Fixed, changed emacsclient to check for TERM=eterm.  The face
    complaints seem to be caused by bugs in term.el; they are not
@@ -976,14 +939,14 @@ DIARY OF CHANGES
 -- Find out the best way to support suspending Emacs with multiple
    ttys.  My guess: disable it on the controlling tty, but from other
    ttys pass it on to emacsclient somehow.  (It is (I hope) trivial to
-   extend emacsclient to handle suspend/resume.  A `kill -STOP' almost
+   extend emacsclient to handle suspend/resume.  A 'kill -STOP' almost
    works right now.)
 
    (Done.  I needed to play with signal handling and the server
    protocol a bit to make emacsclient behave as a normal UNIX program
    wrt foreground/background process groups.)
 
--- There is a flicker during the startup of `emacs -nw'; it's as if
+-- There is a flicker during the startup of 'emacs -nw'; it's as if
    the terminal is initialized, reset and then initialized again.
    Debug this.  (Hint: narrow_foreground_group is called twice during
    startup.)
@@ -1006,7 +969,7 @@ DIARY OF CHANGES
 
    (It was an internal interface that may be changed when necessary.)
 
--- Change Lisp code not to (getenv "TERM"); use the `tty-type' frame
+-- Change Lisp code not to (getenv "TERM"); use the 'tty-type' frame
    parameter or the frame-tty-type function instead.  (M-x tags-search
    "TERM" helps with this.)  Update: Actually, all getenv invocations
    should be checked for multi-tty compatibility, and an interface
@@ -1016,7 +979,7 @@ DIARY OF CHANGES
    calls should be mostly left as they are.)
 
 -- Add an elaborate mechanism for display-local variables.  (There are
-   already a few of these; search for `terminal-local' in the Elisp
+   already a few of these; search for 'terminal-local' in the Elisp
    manual.)
 
    (Not needed.  Display-local variables could be emulated by
@@ -1035,7 +998,7 @@ DIARY OF CHANGES
    emacsclient process for server tty frames.)
    (Update: Not really; Vlocale_coding_system is still global.)
 
--- Make `struct display' accessible to Lisp programs.  Accessor functions:
+-- Make 'struct display' accessible to Lisp programs.  Accessor functions:
 
         (displayp OBJECT):  Returns t if OBJECT is a display.
                 => Implemented as display-live-p.
@@ -1053,7 +1016,7 @@ DIARY OF CHANGES
                 => Already implemented, see frames-on-display-list.
 
         (display-type DISPLAY):  Returns the type of DISPLAY, as a
-                symbol.  (See `framep'.)
+                symbol.  (See 'framep'.)
                 => Implemented as display-live-p.
 
         (display-device DISPLAY): Returns the name of the device that
@@ -1085,20 +1048,8 @@ DIARY OF CHANGES
 
    (Done.)
 
--- Miles Bader suggests that C-x C-c on an emacsclient frame should
-   only close the frame, not exit the entire Emacs session.  Update:
-   see above for a function that does this.  Maybe this should be the
-   new default?
-
-   (Done.  This is the new default.  No complaints so far.)
-
--- Clean up the frame-local variable system.  I think it's ugly and
-   error-prone.  But maybe I just haven't yet fully understood it.
-
-   (Nothing to do.  It doesn't seem ugly any more.  It's rather clever.)
-
 -- Support multiple character locales.  A version of
-   `set-locale-environment' needs to be written for setting up
+   'set-locale-environment' needs to be written for setting up
    display-local settings on ttys.  I think calling
    set-display-table-and-terminal-coding-system and
    set-keyboard-coding-system would be enough.  The language
@@ -1111,21 +1062,9 @@ DIARY OF CHANGES
    them to tweak only frame-local settings, if possible.  (They tend
    to call define-key to set function key sequences a lot.)
 
-   (Done, by making `function-key-map' terminal-local (i.e., part of
+   (Done, by making 'function-key-map' terminal-local (i.e., part of
    struct kboard).  This has probably covered all the remaining problems.)
 
--- Make `function-key-map' and `key-translation-map' terminal-local.
-
-   (Done.)
-
--- Implement `terminal-local-value' and `set-terminal-local-value' to
-   allow deterministic access to terminal local bindings.  The
-   encode-kb package can not set up `key-translation-map' without
-   these.  The terminal-local bindings seem to be independent of what
-   frame is selected.
-
-   (Done.)
-
 -- xt-mouse.el needs to be adapted for multi-tty.  It currently
    signals an error on kill-emacs under X, which prevents the user
    from exiting Emacs. (Reported by Mnemonikk on freenode.)
@@ -1140,8 +1079,8 @@ DIARY OF CHANGES
 
    This only seems to affect displays that are of the same terminfo
    type as the selected one. Interestingly, in screen Emacs normally
-   reports the up arrow key as `M-o A', but after the above SNAFU, it
-   complains about `M-[ a'.  UNIX ttys are a complete mystery to me,
+   reports the up arrow key as 'M-o A', but after the above SNAFU, it
+   complains about 'M-[ a'.  UNIX ttys are a complete mystery to me,
    but it seems the reset-reinitialize cycle somehow leaves the
    non-selected terminals in a different state than usual.  I have no
    idea how this could happen.
@@ -1189,15 +1128,15 @@ DIARY OF CHANGES
    clear what binding is in effect in any given time.  See if
    current_kboard (or at least the terminal-local bindings exported to
    Lisp) might be changed to be tied to the selected frame instead.
-   Currently, `function-key-map' and `key-translation-map' may be
+   Currently, 'function-key-map' and 'key-translation-map' may be
    accessed reliably only using the hackish
-   `(set-)terminal-local-value' functions.
+   '(set-)terminal-local-value' functions.
 
-   Perhaps there should be a difference between `last-command' &co.
+   Perhaps there should be a difference between 'last-command' &co.
    and these more conventional configuration variables.
-   (E.g. `symbol-value' would use current_kboard to access
-   `last-command', but SELECTED_FRAME()->display->kboard to get the
-   value of `function-key-map'.
+   (E.g. 'symbol-value' would use current_kboard to access
+   'last-command', but SELECTED_FRAME()->display->kboard to get the
+   value of 'function-key-map'.
 
    (Fixed in patch-434.)
 
@@ -1208,7 +1147,7 @@ DIARY OF CHANGES
    below" was the set-input-mode madness.)
 
    (Update: this bug was fixed for good in patch-449.  It was tracked
-   down to a bug in `read_key_sequence': it failed to reinitialize its
+   down to a bug in 'read_key_sequence': it failed to reinitialize its
    local function-key-map/key-translation-map references when it
    switched keyboards.  I don't understand why did this bug only
    appear on brand new frames, though!)
@@ -1220,35 +1159,35 @@ DIARY OF CHANGES
 -- Implement automatic forwarding of client environment variables to
    forked processes, as discussed on the multi-tty list.  Terminal
    parameters are now accessible in C code, so the biggest obstacle is
-   gone.  The `getenv_internal' and `child_setup' functions in
+   gone.  The 'getenv_internal' and 'child_setup' functions in
    callproc.c must be changed to support the following variable:
 
         terminal-local-environment-variables is a variable defined in ...
 
         Enable or disable terminal-local environment variables.
 
-        If set to t, `getenv', `setenv' and subprocess creation
+        If set to t, 'getenv', 'setenv' and subprocess creation
         functions use the environment variables of the emacsclient
         process that created the selected frame, ignoring
-        `process-environment'.
+        'process-environment'.
 
-        If set to nil, Emacs uses `process-environment' and ignores
+        If set to nil, Emacs uses 'process-environment' and ignores
         the client environment.
 
-        Otherwise, `terminal-local-environment-variables' should be a
+        Otherwise, 'terminal-local-environment-variables' should be a
         list of variable names (represented by Lisp strings) to look
         up in the client environment.  The rest will come from
-        `process-environment'.
+        'process-environment'.
 
-   (Implemented in patch-461; `terminal-getenv', `terminal-setenv' and
-   `with-terminal-environment' are now replaced by extensions to
-   `getenv' and `setenv', and the new `local-environment-variables'
+   (Implemented in patch-461; 'terminal-getenv', 'terminal-setenv' and
+   'with-terminal-environment' are now replaced by extensions to
+   'getenv' and 'setenv', and the new 'local-environment-variables'
    facility.  Yay!)
 
    (Updated in patch-465 to fix the semantics of let-binding
-   `process-environment'.  `process-environment' was changed to
+   'process-environment'.  'process-environment' was changed to
    override all local/global environment variables, and a new variable
-   `global-environment' was introduced to have `process-environment's
+   'global-environment' was introduced to have 'process-environment's
    old meaning.)
 
    (Updated in patch-466 to fix the case when two emacsclient sessions
@@ -1256,27 +1195,27 @@ DIARY OF CHANGES
    environment lists are now stored as frame parameters, so the
    C-level terminal parameters are not strictly necessary any more.)
 
--- `Fdelete_frame' is called from various critical places where it is
+-- 'Fdelete_frame' is called from various critical places where it is
    not acceptable for the frame deletion to fail, e.g. from
-   x_connection_closed after an X error.  `Fdelete_frame' now protects
-   against `delete-frame-functions' throwing an error and preventing a
+   x_connection_closed after an X error.  'Fdelete_frame' now protects
+   against 'delete-frame-functions' throwing an error and preventing a
    frame delete. (patch-475)
 
 -- Fix set-input-mode for multi-tty.  It's a truly horrible interface;
    what if we'd blow it up into several separate functions (with a
    compatibility definition)?
 
-   (Done.  See `set-input-interrupt-mode', `set-output-flow-control',
-   `set-input-meta-mode' and `set-quit-char'.) (patch-457)
+   (Done.  See 'set-input-interrupt-mode', 'set-output-flow-control',
+   'set-input-meta-mode' and 'set-quit-char'.) (patch-457)
 
--- Let-binding `overriding-terminal-local-map' on a brand new frame
-   does not seem to work correctly.  (See `fancy-splash-screens'.)
+-- Let-binding 'overriding-terminal-local-map' on a brand new frame
+   does not seem to work correctly.  (See 'fancy-splash-screens'.)
    The keymap seems to be set up right, but events go to another
-   terminal.  Or is it `unread-command-events' that gets Emacs
+   terminal.  Or is it 'unread-command-events' that gets Emacs
    confused?  Investigate.
 
    (Emacs was confused because a process filter entered
-   `recursive-edit' while Emacs was reading input.  I added support
+   'recursive-edit' while Emacs was reading input.  I added support
    for this in the input system.) (patch-489)
 
 -- I smell something funny around pop_kboard's "deleted kboard" case.
@@ -1301,7 +1240,7 @@ DIARY OF CHANGES
    synchronously (with wait_reading_process_input), or asynchronously
    by SIGIO or polling (SIGALRM).  C-g either sets the Vquit_flag,
    signals a 'quit condition (when immediate_quit), or throws to
-   `getcjmp' when Emacs was waiting for input when the C-g event
+   'getcjmp' when Emacs was waiting for input when the C-g event
    arrived.)
 
 -- Replace wrong_kboard_jmpbuf with a special return value of
@@ -1310,7 +1249,7 @@ DIARY OF CHANGES
 
    (Done in patch-500.)
 
--- `tool-bar-mode', `scroll-bar-mode', `menu-bar-mode' and
+-- 'tool-bar-mode', 'scroll-bar-mode', 'menu-bar-mode' and
    'fringe-mode' are modes global to the entire Emacs session, not
    just a single frame or a single terminal.  This means that their
    status sometimes differs from what's actually displayed on the
@@ -1323,7 +1262,7 @@ DIARY OF CHANGES
 
    (Done in patch-537.)
 
--- The `default-directory' variable should somehow be set to the
+-- The 'default-directory' variable should somehow be set to the
    cwd of the emacsclient process when the user runs emacsclient
    without file arguments.  Perhaps it is OK to just override the
    directory of the *scratch* buffer.
@@ -1335,9 +1274,9 @@ DIARY OF CHANGES
    frame parameter) is not filled with the correct background color.
 
    It seems the border contents are drawn onto by the
-   update_single_window call in `x-show-tip'.  After some debugging, I
+   update_single_window call in 'x-show-tip'.  After some debugging, I
    think the window's background color is not set up
-   correctly---calling `x_clear_area' fills the specified area with
+   correctly---calling 'x_clear_area' fills the specified area with
    black, not light yellow.
 
    (Done in patch-544.  A background_pixel field was defined both in
diff --git a/admin/notes/newfile b/admin/notes/newfile
index 0b66b8054bb..072e966d60c 100644
--- a/admin/notes/newfile
+++ b/admin/notes/newfile
@@ -6,7 +6,7 @@ CHECKLIST FOR ADDING A NEW FILE TO EMACS -*- outline -*-
 format, copyright and license notice, etc).
 
 ** Make sure the filename does not cause the DOS port any problems (8+3).
-Run the `doschk' program like this:
+Run the 'doschk' program like this:
 
     find /path/to/emacs -print | doschk
 
@@ -15,7 +15,7 @@ output under the headings "The following files are not valid DOS file
 names:" and "The following resolve to the same DOS file names:" should
 not include any files that end up in the release tarball.
 
-** Make the ChangeLog entry in the name of the author(s), not your own name.
+** Commit in the name of the author(s), not your own name.
 
 ** If appropriate, check that the file compiles OK and that Emacs
 builds fine with it.  Address any compilation warnings.
diff --git a/admin/notes/repo b/admin/notes/repo
new file mode 100644
index 00000000000..b27a3f42891
--- /dev/null
+++ b/admin/notes/repo
@@ -0,0 +1,136 @@
+NOTES ON COMMITTING TO EMACS'S REPOSITORY    -*- outline -*-
+
+** elpa
+
+This branch does not contain a copy of Emacs, but of the Emacs Lisp
+package archive (elpa.gnu.org).  See admin/notes/elpa for further
+explanation, and the README file in the branch for usage
+instructions.
+
+* Install changes only on one branch, let them get merged elsewhere if needed.
+
+In particular, install bug-fixes only on the release branch (if there
+is one) and let them get synced to the master; do not install them by
+hand on the master as well.  E.g. if there is an active "emacs-24" branch
+and you have a bug-fix appropriate for the next emacs-24.x release,
+install it only on the emacs-24 branch, not on the master as well.
+
+Installing things manually into more than one branch makes merges more
+difficult.
+
+http://lists.gnu.org/archive/html/emacs-devel/2010-03/msg01124.html
+
+The exception is, if you know that the change will be difficult to
+merge to the master (eg because the master code has changed a lot).
+In that case, it's helpful if you can apply the change to both master
+and branch yourself (when committing the branch change, indicate
+in the commit log that it should not be merged to the master, by
+including the phrase "Not to be merged to master", or any other phrase
+that matches "merge").
+
+* Installing changes from your personal branches.
+
+If your branch has only a single commit, or many different real
+commits, it is fine to do a merge.  If your branch has only a very
+small number of "real" commits, but several "merge from masters", it is
+preferred that you take your branch's diff, apply it to the master, and
+commit directly, not merge.  This keeps the history cleaner.
+
+In general, when working on some feature in a separate branch, it is
+preferable not to merge from master until you are done with the
+feature.  Unless you really need some change that was done on the
+master while you were developing on the branch, you don't really need
+those merges; just merge once, when you are done with the feature, and
+Bazaar will take care of the rest.  Bazaar is much better in this than
+CVS, so interim merges are unnecessary.
+
+Or use shelves; or rebase; or do something else.  See the thread for
+yet another fun excursion into the exciting world of version control.
+
+http://lists.gnu.org/archive/html/emacs-devel/2010-04/msg00086.html
+
+* Installing changes from gnulib
+
+Some of the files in Emacs are copied from gnulib.  To synchronize
+these files from the version of gnulib that you have checked out into
+a sibling directory of your branch, type "admin/merge-gnulib"; this
+will check out the latest version of gnulib if there is no sibling
+directory already.  It is a good idea to run "git status" afterwards,
+so that if a gnulib module added a file, you can record the new file
+using "git add".  After synchronizing from gnulib, do a "make" in the
+usual way.
+
+To change the set of gnulib modules, change the GNULIB_MODULES
+variable in admin/merge-gnulib before running it.
+
+If you remove a gnulib module, or if a gnulib module
+removes a file, then remove the corresponding files by hand.
+
+* How to merge changes from emacs-24 to master
+
+[The section on git merge procedure has not yet been written.]
+
+You may see conflicts in autoload md5sums in comments.  Strictly
+speaking, the right thing to do is merge everything else, resolve the
+conflict by choosing either the master or branch version, then run
+'make -C lisp autoloads' to update the md5sums to the correct master
+value before committing.
+
+* Re-adding a file that has been removed from the repository
+
+Let's suppose you've done:
+
+git rm file; git commit -a
+
+You can just restore a copy of the file and then re-add it;
+git does not have per-file history so this will not harm
+anything.
+
+Alternatively, you can do
+
+git revert XXXXX
+
+where XXXXX is the hash of the commit in which file was removed.
+This backs out the entire changeset the deletion was part of,
+which is often more appropriate.
+
+* Undoing a commit (uncommitting)
+
+If you have not pushed the commit, you may be able to use 'git reset
+--hard' with a hash argument to revert the your local repo copy to the
+pre-commit state.
+
+If you have pushed  commit, resetting will be ineffective because it
+will only vanish the commit in your local copy.  Instead, use 'git
+revert', giving it the commit ID as argument. This will create a
+new commit that backs out the change. Then push that.
+
+Note that git will generate a log message for the revert that includes
+a git hash.  Please edit this to refer to the commit by the first line
+of its log comment, or by committer and date, or by something else
+that is not the hash.  As noted previously, it is best to avoid hashes
+in comments in case we someday have to change version-control systems
+again.
+
+* Bisecting
+
+This is a semi-automated way to find the revision that introduced a bug.
+Browse 'git help bisect' for technical instructions.
+
+* Maintaining ChangeLog history
+
+Older ChangeLog entries are kept in history files named ChangeLog.1,
+ChangeLog.2, etc., and can be edited just as any other source files
+can.  Newer ChangeLog entries are stored in the repository as commit
+messages, which cannot be edited directly.
+
+'make ChangeLog' copies newer ChangeLog entries into a file
+'ChangeLog' that is intended to be put into the distribution tarball.
+This ChangeLog file is not put into the repository.
+
+'make change-history' copies all newer ChangeLog entries into the
+start of the newest ChangeLog history file.  These ChangeLog entries
+are thereafter considered to be old, so later uses of 'make ChangeLog'
+and/or 'make change-history' will no longer copy the entries.  To
+alter ChangeLog history, run 'make change-history', then edit
+the ChangeLog history files manually and commit your changes.
diff --git a/admin/notes/tags b/admin/notes/tags
index 9c3700f2e4d..a1e1b86429c 100644
--- a/admin/notes/tags
+++ b/admin/notes/tags
@@ -5,1002 +5,999 @@ and hence were removed.  See:
 
 http://lists.gnu.org/archive/html/emacs-devel/2012-04/msg00042.html
 
-(UPDATE: It seems tag deletion is basically impossible in bzr, so all
-these tags came back.)
-
 In the unlikely event that you need them, the removed tags were:
 
-tag                       revision
+tag                       version stamp
 
-amigados-merge            14846
-before-thomas-posix1996   16843
-gcc-2_8_1-980401          20893
-gcc-2_8_1-980402          21795
-gcc-2_8_1-980407          20893
-gcc-2_8_1-980412          20893
-gcc-2_8_1-980413          20893
-gcc-2_8_1-980419          21502
-gcc-2_8_1-980426          21502
-gcc-2_8_1-980502          21795
-gcc-2_8_1-980513          21795
-gcc-2_8_1-980525          22147
-gcc-2_8_1-980529          22147
-gcc-2_8_1-980608          22147
-gcc-2_8_1-980609          22147
-gcc-2_8_1-980627          22478
-gcc-2_8_1-980705          22478
-gcc-2_8_1-980718          22478
-gcc-2_8_1-980811          22971
-gcc-2_8_1-980813          23005
-gcc-2_8_1-980928          23338
-gcc-2_8_1-980929          23338
-gcc-2_8_1-RELEASE         20893
-gcc_2_8_1-980315          20893
-gcc_2_8_1-980929          23338
-glibc-2_0_2               16843
-gnumach-release-1-1       17693
-gnumach-release-1-1-1     17693
-gnumach-release-1-1-2     18209
-gnumach-release-1-1-3     18209
-hurd-release-0-2          18209
-jimb-sync-Nov-3-1992       1552
-libc20x-97031             16843
-libc20x-970306            16843
-libc20x-970316            16843
-libc20x-970318            16843
-libc20x-970319            16843
-libc20x-970404            16843
-libc-1-90                 15360
-libc-1-91                 15451
-libc-1-92                 15463
-libc-1-93                 15702
-libc-950402               11085
-libc-950411               11255
-libc-950722               12418
-libc-950723               12418
-libc-950922               12859
-libc-951016               12859
-libc-951018               13231
-libc-951029               13231
-libc-951031               13231
-libc-951101               13231
-libc-951102               13231
-libc-951103               13231
-libc-951104               13231
-libc-951105               13231
-libc-951106               13231
-libc-951107               13231
-libc-951108               13231
-libc-951109               13231
-libc-951110               13231
-libc-951111               13231
-libc-951112               13231
-libc-951113               13231
-libc-951114               13231
-libc-951115               13231
-libc-951116               13231
-libc-951117               13231
-libc-951118               13231
-libc-951119               13231
-libc-951120               13231
-libc-951121               13231
-libc-951122               13231
-libc-951123               13231
-libc-951124               13231
-libc-951125               13231
-libc-951126               13231
-libc-951127               13231
-libc-951128               13231
-libc-951129               13231
-libc-951130               13231
-libc-951201               13679
-libc-951202               13679
-libc-951203               13679
-libc-951204               13679
-libc-951206               13686
-libc-951208               13693
-libc-951209               13693
-libc-951210               13693
-libc-951211               13693
-libc-951212               13704
-libc-951213               13704
-libc-951214               13730
-libc-951215               13730
-libc-951216               13741
-libc-951217               13741
-libc-951218               13741
-libc-951219               13741
-libc-951220               13741
-libc-951221               13741
-libc-951222               13741
-libc-951223               13741
-libc-951224               13741
-libc-951225               13741
-libc-951226               13741
-libc-951227               13741
-libc-951228               13741
-libc-951229               13741
-libc-951230               13741
-libc-951231               13741
-libc-960101               13741
-libc-960102               13741
-libc-960103               13741
-libc-960104               13741
-libc-960105               13741
-libc-960106               13741
-libc-960107               13741
-libc-960108               13741
-libc-960109               13741
-libc-960110               13741
-libc-960111               13741
-libc-960112               13741
-libc-960113               13741
-libc-960114               13741
-libc-960115               13741
-libc-960116               14192
-libc-960117               14192
-libc-960118               14213
-libc-960119               14213
-libc-960120               14213
-libc-960121               14213
-libc-960122               14213
-libc-960123               14213
-libc-960124               14213
-libc-960125               14213
-libc-960126               14213
-libc-960127               14213
-libc-960128               14213
-libc-960129               14213
-libc-960130               14213
-libc-960131               14213
-libc-960201               14449
-libc-960202               14449
-libc-960203               14473
-libc-960204               14473
-libc-960205               14473
-libc-960206               14473
-libc-960207               14473
-libc-960208               14473
-libc-960209               14473
-libc-960210               14473
-libc-960211               14540
-libc-960212               14548
-libc-960213               14562
-libc-960214               14562
-libc-960215               14562
-libc-960216               14562
-libc-960217               14562
-libc-960218               14562
-libc-960219               14562
-libc-960220               14562
-libc-960221               14562
-libc-960222               14562
-libc-960223               14562
-libc-960224               14562
-libc-960225               14562
-libc-960226               14562
-libc-960227               14562
-libc-960228               14562
-libc-960229               14562
-libc-960302               14724
-libc-960303               14724
-libc-960304               14724
-libc-960305               14753
-libc-960306               14764
-libc-960307               14764
-libc-960308               14764
-libc-960309               14764
-libc-960310               14764
-libc-960311               14764
-libc-960312               14764
-libc-960313               14764
-libc-960314               14764
-libc-960315               14809
-libc-960316               14809
-libc-960317               14809
-libc-960318               14809
-libc-960319               14809
-libc-960320               14809
-libc-960321               14809
-libc-960322               14855
-libc-960323               14855
-libc-960324               14855
-libc-960325               14855
-libc-960326               14855
-libc-960327               14855
-libc-960328               14855
-libc-960329               14912
-libc-960330               14912
-libc-960331               14912
-libc-960401               14912
-libc-960402               14912
-libc-960403               14912
-libc-960404               14912
-libc-960405               14912
-libc-960406               14912
-libc-960407               14912
-libc-960408               14912
-libc-960409               14962
-libc-960410               14962
-libc-960411               14962
-libc-960412               14962
-libc-960413               15014
-libc-960414               15014
-libc-960415               15014
-libc-960416               15014
-libc-960417               15014
-libc-960418               15014
-libc-960419               15014
-libc-960420               15014
-libc-960421               15014
-libc-960422               15014
-libc-960423               15014
-libc-960424               15014
-libc-960425               15014
-libc-960426               15014
-libc-960427               15014
-libc-960428               15014
-libc-960429               15014
-libc-960430               15014
-libc-960501               15014
-libc-960502               15014
-libc-960503               15014
-libc-960504               15014
-libc-960505               15014
-libc-960506               15014
-libc-960507               15014
-libc-960508               15014
-libc-960509               15014
-libc-960510               15014
-libc-960511               15014
-libc-960512               15014
-libc-960513               15014
-libc-960514               15014
-libc-960515               15014
-libc-960516               15014
-libc-960517               15014
-libc-960518               15014
-libc-960519               15014
-libc-960520               15014
-libc-960521               15261
-libc-960522               15278
-libc-960523               15278
-libc-960524               15278
-libc-960525               15287
-libc-960526               15287
-libc-960527               15287
-libc-960528               15287
-libc-960529               15287
-libc-960530               15287
-libc-960531               15287
-libc-960601               15287
-libc-960602               15287
-libc-960603               15287
-libc-960604               15319
-libc-960605               15334
-libc-960606               15334
-libc-960607               15334
-libc-960608               15360
-libc-960609               15360
-libc-960610               15360
-libc-960611               15360
-libc-960612               15360
-libc-960613               15360
-libc-960614               15360
-libc-960615               15360
-libc-960616               15360
-libc-960617               15360
-libc-960618               15360
-libc-960619               15451
-libc-960620               15451
-libc-960621               15463
-libc-960622               15463
-libc-960623               15463
-libc-960624               15463
-libc-960625               15463
-libc-960626               15463
-libc-960627               15463
-libc-960628               15463
-libc-960629               15554
-libc-960630               15554
-libc-960701               15554
-libc-960702               15554
-libc-960703               15554
-libc-960704               15554
-libc-960705               15554
-libc-960706               15554
-libc-960707               15554
-libc-960708               15620
-libc-960709               15620
-libc-960710               15620
-libc-960711               15620
-libc-960712               15620
-libc-960713               15620
-libc-960714               15620
-libc-960715               15673
-libc-960716               15702
-libc-960717               15702
-libc-960718               15702
-libc-960719               15702
-libc-960720               15702
-libc-960721               15702
-libc-960722               15702
-libc-960723               15702
-libc-960724               15702
-libc-960725               15702
-libc-960726               15702
-libc-960727               15702
-libc-960728               15702
-libc-960729               15702
-libc-960730               15702
-libc-960731               15702
-libc-960801               15702
-libc-960802               15702
-libc-960803               15702
-libc-960804               15702
-libc-960805               15702
-libc-960806               15702
-libc-960807               15702
-libc-960808               15702
-libc-960809               15702
-libc-960810               15702
-libc-960811               15702
-libc-960812               15702
-libc-960813               15702
-libc-960814               15702
-libc-960815               15702
-libc-960816               15702
-libc-960817               15702
-libc-960818               15702
-libc-960819               15702
-libc-960820               15702
-libc-960821               15702
-libc-960822               15702
-libc-960823               15702
-libc-960824               15702
-libc-960825               15702
-libc-960826               15702
-libc-960827               15702
-libc-960828               15702
-libc-960829               15702
-libc-960830               15702
-libc-960831               15702
-libc-960901               15702
-libc-960902               15702
-libc-960903               15702
-libc-960904               15702
-libc-960905               15702
-libc-960906               15702
-libc-960907               15702
-libc-960908               15702
-libc-960909               15702
-libc-960910               15702
-libc-960911               15702
-libc-960912               15702
-libc-960913               16178
-libc-960918               16190
-libc-960919               16190
-libc-960920               16190
-libc-960921               16190
-libc-960922               16190
-libc-960923               16190
-libc-960925               16307
-libc-960926               16307
-libc-960927               16307
-libc-960928               16307
-libc-960929               16307
-libc-961001               16307
-libc-961004               16307
-libc-961005               16307
-libc-961006               16307
-libc-961007               16307
-libc-961008               16307
-libc-961009               16307
-libc-961010               16307
-libc-961011               16307
-libc-961012               16307
-libc-961013               16307
-libc-961014               16307
-libc-961015               16307
-libc-961016               16307
-libc-961017               16307
-libc-961018               16307
-libc-961019               16307
-libc-961020               16307
-libc-961021               16307
-libc-961022               16307
-libc-961023               16307
-libc-961024               16307
-libc-961025               16307
-libc-961026               16307
-libc-961027               16307
-libc-961028               16307
-libc-961029               16482
-libc-961030               16482
-libc-961031               16482
-libc-961101               16482
-libc-961102               16482
-libc-961103               16482
-libc-961104               16482
-libc-961105               16482
-libc-961106               16482
-libc-961107               16482
-libc-961108               16540
-libc-961109               16540
-libc-961110               16540
-libc-961111               16540
-libc-961114               16576
-libc-961115               16576
-libc-961116               16576
-libc-961117               16576
-libc-961118               16576
-libc-961119               16576
-libc-961120               16601
-libc-961121               16602
-libc-961203               16607
-libc-961204               16607
-libc-961205               16607
-libc-961206               16607
-libc-961207               16607
-libc-961208               16638
-libc-961209               16638
-libc-961210               16638
-libc-961211               16664
-libc-961212               16664
-libc-961213               16664
-libc-961214               16664
-libc-961215               16664
-libc-961216               16664
-libc-961217               16664
-libc-961218               16664
-libc-961219               16664
-libc-961220               16664
-libc-961221               16664
-libc-961222               16664
-libc-961223               16664
-libc-961224               16664
-libc-961225               16664
-libc-961226               16664
-libc-961227               16664
-libc-961228               16664
-libc-961229               16664
-libc-961230               16664
-libc-961231               16664
-libc-970101               16802
-libc-970102               16802
-libc-970103               16802
-libc-970104               16821
-libc-970105               16833
-libc-970106               16833
-libc-970107               16833
-libc-970108               16843
-libc-970109               16843
-libc-970110               16843
-libc-970111               16843
-libc-970112               16843
-libc-970113               16843
-libc-970114               16843
-libc-970115               16843
-libc-970116               16843
-libc-970117               16843
-libc-970118               16843
-libc-970119               16843
-libc-970120               16843
-libc-970121               16843
-libc-970122               16843
-libc-970123               16843
-libc-970124               16843
-libc-970125               16843
-libc-970126               16843
-libc-970127               16843
-libc-970128               16843
-libc-970129               16843
-libc-970130               16843
-libc-970131               16843
-libc-970201               16843
-libc-970202               16843
-libc-970203               16843
-libc-970204               16843
-libc-970205               16843
-libc-970206               16843
-libc-970207               16843
-libc-970208               16843
-libc-970209               16843
-libc-970210               16843
-libc-970211               16843
-libc-970212               16843
-libc-970213               16843
-libc-970214               16843
-libc-970215               16843
-libc-970216               16843
-libc-970217               16843
-libc-970218               16843
-libc-970219               16843
-libc-970220               16843
-libc-970221               16843
-libc-970222               16843
-libc-970223               16843
-libc-970224               16843
-libc-970225               16843
-libc-970226               16843
-libc-970227               16843
-libc-970228               16843
-libc-970301               16843
-libc-970302               16843
-libc-970303               16843
-libc-970304               16843
-libc-970305               16843
-libc-970306               16843
-libc-970307               16843
-libc-970308               16843
-libc-970309               16843
-libc-970310               16843
-libc-970311               16843
-libc-970312               16843
-libc-970313               16843
-libc-970314               16843
-libc-970315               16843
-libc-970316               16843
-libc-970317               16843
-libc-970318               16843
-libc-970319               16843
-libc-970320               16843
-libc-970321               16843
-libc-970322               16843
-libc-970323               16843
-libc-970324               16843
-libc-970325               17242
-libc-970326               17242
-libc-970327               17242
-libc-970328               17242
-libc-970329               17242
-libc-970330               17242
-libc-970331               17242
-libc-970401               17242
-libc-970402               17242
-libc-970403               17242
-libc-970404               17242
-libc-970405               17242
-libc-970406               17242
-libc-970407               17242
-libc-970408               17242
-libc-970409               17242
-libc-970410               17242
-libc-970411               17242
-libc-970412               17404
-libc-970413               17404
-libc-970414               17404
-libc-970415               17404
-libc-970416               17404
-libc-970417               17404
-libc-970418               17500
-libc-970419               17500
-libc-970420               17500
-libc-970421               17500
-libc-970422               17500
-libc-970423               17500
-libc-970424               17500
-libc-970425               17500
-libc-970426               17500
-libc-970427               17500
-libc-970428               17500
-libc-970429               17500
-libc-970430               17500
-libc-970501               17500
-libc-970502               17500
-libc-970503               17500
-libc-970504               17500
-libc-970505               17500
-libc-970506               17675
-libc-970507               17675
-libc-970508               17693
-libc-970509               17693
-libc-970510               17693
-libc-970511               17693
-libc-970512               17693
-libc-970513               17693
-libc-970514               17693
-libc-970515               17693
-libc-970516               17693
-libc-970517               17693
-libc-970518               17693
-libc-970519               17693
-libc-970520               17693
-libc-970521               17693
-libc-970522               17693
-libc-970523               17693
-libc-970524               17693
-libc-970525               17693
-libc-970526               17693
-libc-970527               17693
-libc-970528               17693
-libc-970529               17693
-libc-970530               17693
-libc-970531               17693
-libc-970601               17693
-libc-970602               17693
-libc-970603               17693
-libc-970604               17693
-libc-970605               17693
-libc-970606               18148
-libc-970607               18148
-libc-970608               18164
-libc-970609               18174
-libc-970610               18209
-libc-970611               18209
-libc-970612               18209
-libc-970613               18209
-libc-970614               18209
-libc-970615               18209
-libc-970616               18209
-libc-970617               18209
-libc-970618               18209
-libc-970619               18209
-libc-970620               18209
-libc-970621               18209
-libc-970622               18209
-libc-970624               18421
-libc-970625               18421
-libc-970626               18421
-libc-970627               18421
-libc-970628               18473
-libc-970629               18473
-libc-970630               18473
-libc-970701               18473
-libc-970702               18473
-libc-970703               18473
-libc-970704               18473
-libc-970705               18473
-libc-970707               18663
-libc-970708               18663
-libc-970709               18663
-libc-970710               18663
-libc-970713               18663
-libc-970715               18780
-libc-970717               18824
-libc-970718               18824
-libc-970719               18824
-libc-970720               18824
-libc-970721               18889
-libc-970722               18889
-libc-970723               18889
-libc-970724               18889
-libc-970725               18889
-libc-970726               18889
-libc-970727               19000
-libc-970728               19000
-libc-970729               19030
-libc-970730               19030
-libc-970731               19030
-libc-970801               19030
-libc-970802               19074
-libc-970803               19074
-libc-970804               19074
-libc-970805               19074
-libc-970806               19074
-libc-970807               19074
-libc-970808               19074
-libc-970809               19074
-libc-970810               19074
-libc-970811               19074
-libc-970812               19074
-libc-970813               19074
-libc-970814               19074
-libc-970815               19074
-libc-970816               19074
-libc-970817               19074
-libc-970818               19074
-libc-970819               19074
-libc-970820               19074
-libc-970821               19074
-libc-970822               19074
-libc-970823               19472
-libc-970824               19472
-libc-970825               19472
-libc-970826               19472
-libc-970827               19541
-libc-970828               19541
-libc-970829               19541
-libc-970830               19541
-libc-970831               19541
-libc-970901               19541
-libc-970902               19541
-libc-970903               19541
-libc-970904               19541
-libc-970905               19541
-libc-970906               19766
-libc-970907               19766
-libc-970908               19766
-libc-970911               19861
-libc-970912               19861
-libc-970913               19861
-libc-970914               19861
-libc-970915               19861
-libc-970916               19861
-libc-970917               19861
-libc-970918               19861
-libc-970919               19861
-libc-970920               19861
-libc-970921               19861
-libc-970922               19861
-libc-970923               19861
-libc-970924               19861
-libc-970925               19861
-libc-970926               19861
-libc-970927               19861
-libc-970928               19861
-libc-970929               19861
-libc-970930               19861
-libc-971001               19861
-libc-971018               19861
-libc-971019               19861
-libc-971020               19861
-libc-971021               19861
-libc-971022               19861
-libc-971023               19861
-libc-971024               19861
-libc-971025               19861
-libc-971026               19861
-libc-971027               19861
-libc-971028               19861
-libc-971029               19861
-libc-971030               19861
-libc-971031               19861
-libc-971101               19861
-libc-971102               19861
-libc-971103               19861
-libc-971104               19861
-libc-971105               19861
-libc-971106               19861
-libc-971107               19861
-libc-971108               19861
-libc-971109               19861
-libc-971110               19861
-libc-971111               19861
-libc-971112               19861
-libc-971113               19861
-libc-971114               19861
-libc-971115               19861
-libc-971116               19861
-libc-971117               19861
-libc-971118               19861
-libc-971120               19861
-libc-971121               19861
-libc-971122               19861
-libc-971123               19861
-libc-971124               19861
-libc-971125               19861
-libc-971126               19861
-libc-971127               19861
-libc-971128               19861
-libc-971129               19861
-libc-971130               19861
-libc-971201               19861
-libc-971203               19861
-libc-971204               19861
-libc-971205               19861
-libc-971206               19861
-libc-971207               19861
-libc-971208               19861
-libc-971209               19861
-libc-971210               19861
-libc-971211               19861
-libc-971212               19861
-libc-971213               19861
-libc-971214               19861
-libc-971217               19861
-libc-971218               19861
-libc-971219               19861
-libc-971220               19861
-libc-971221               19861
-libc-971222               19861
-libc-971223               19861
-libc-971224               19861
-libc-971225               19861
-libc-971226               19861
-libc-971227               19861
-libc-971228               19861
-libc-971229               19861
-libc-971230               19861
-libc-971231               19861
-libc-980103               19861
-libc-980104               19861
-libc-980105               19861
-libc-980106               19861
-libc-980107               19861
-libc-980108               19861
-libc-980109               19861
-libc-980110               19861
-libc-980111               19861
-libc-980112               19861
-libc-980114               19861
-libc-980115               19861
-libc-980116               19861
-libc-980117               19861
-libc-980118               19861
-libc-980119               19861
-libc-980120               19861
-libc-980121               19861
-libc-980122               19861
-libc-980123               19861
-libc-980124               19861
-libc-980125               19861
-libc-980126               19861
-libc-980127               19861
-libc-980128               19861
-libc-980129               20797
-libc-980130               20797
-libc-980212               20832
-libc-980213               20832
-libc-980214               20893
-libc-980215               20893
-libc-980216               20893
-libc-980217               20893
-libc-980218               20893
-libc-980219               20893
-libc-980220               20893
-libc-980221               20893
-libc-980222               20893
-libc-980223               20893
-libc-980224               20893
-libc-980225               20893
-libc-980226               20893
-libc-980227               20893
-libc-980228               20893
-libc-980301               20893
-libc-980302               20893
-libc-980303               20893
-libc-980304               20893
-libc-980306               20893
-libc-980307               20893
-libc-980308               20893
-libc-980309               20893
-libc-980310               20893
-libc-980311               20893
-libc-980312               20893
-libc-980313               20893
-libc-980314               20893
-libc-980315               20893
-libc-980316               20893
-libc-980317               20893
-libc-980318               20893
-libc-980319               20893
-libc-980320               20893
-libc-980321               20893
-libc-980322               20893
-libc-980323               20893
-libc-980324               20893
-libc-980325               20893
-libc-980326               20893
-libc-980327               20893
-libc-980328               20893
-libc-980329               20893
-libc-980330               20893
-libc-980331               20893
-libc-980401               20893
-libc-980402               20893
-libc-980403               20893
-libc-980404               20893
-libc-980405               20893
-libc-980406               20893
-libc-980407               20893
-libc-980408               20893
-libc-980409               20893
-libc-980410               20893
-libc-980411               20893
-libc-980412               20893
-libc-980413               20893
-libc-980414               20893
-libc-980428               20893
-libc-980429               20893
-libc-980430               20893
-libc-980501               20893
-libc-980502               20893
-libc-980503               20893
-libc-980504               20893
-libc-980505               20893
-libc-980506               20893
-libc-980507               20893
-libc-980508               20893
-libc-980509               20893
-libc-980510               20893
-libc-980512               20893
-libc-980513               20893
-libc-980514               20893
-libc-980515               20893
-libc-980516               20893
-libc-980517               20893
-libc-980518               20893
-libc-980519               20893
-libc-980520               20893
-libc-980521               20893
-libc-980522               20893
-libc-980523               20893
-libc-980524               20893
-libc-980525               20893
-libc-980526               20893
-libc-980527               20893
-libc-980528               20893
-libc-980529               20893
-libc-980530               20893
-libc-980531               20893
-libc-980601               20893
-libc-980602               20893
-libc-980603               20893
-libc-980604               20893
-libc-980605               20893
-libc-980606               20893
-libc-980607               20893
-libc-980608               20893
-libc-980609               20893
-libc-980610               20893
-libc-980611               20893
-libc-980612               20893
-libc-980613               20893
-libc-980614               22478
-libc-980615               22478
-libc-980616               22478
-libc-980617               22478
-libc-980618               22478
-libc-980619               22478
-libc-980620               22478
-libc-980621               22478
-libc-980622               22478
-libc-980623               22478
-libc-980624               22478
-libc-980625               22478
-libc-980626               22478
-libc-980627               22478
-libc-980628               22478
-libc-980629               22478
-libc-980630               22478
-libc-980701               22478
-libc-980702               22478
-libc-980703               22478
-libc-980704               22478
-libc-980705               22478
-libc-980706               22478
-libc-980707               22478
-libc-980708               22478
-libc-980709               22478
-libc-980710               22478
-libc-980711               22478
-libc-980712               22478
-libc-980713               22478
-libc-980714               22478
-libc-980715               22478
-libc-980716               22478
-libc-980717               22478
-libc-980718               22478
-libc-980719               22478
-libc-980720               22787
-libc_1_09                 10803
-make-3-72-9               10364
-make-3-72-10              10364
-make-3-72-11              10364
-make-3-72-12              10364
-make-3-72-13              10364
-make-3-73                 10364
-make-3-73-1               10364
-make-3-73-2               10364
-make-3-73-3               11789
-make-3-74                 11789
-make-3-74-1               12800
-make-3-74-2               12800
-make-3-74-3               14458
-make-3-74-4               14846
-make-3-74-5               15594
-make-3-74-6               15594
-make-3-74-7               15594
-make-3-75                 15594
-make-3-75-1               18912
-make-3-75-91              18912
-make-3-75-92              19342
-make-3-75-93              21502
-make-3-76                 19768
-make-3-76-1               19768
-release-0-0               15702
-release-0-1               15702
-release-1-0               17404
-Release_5_25              24283
-root-libc-2_0_x-branch    16843
+amigados-merge            1996-03-20T01:08:11Z!roland@gnu.org
+before-thomas-posix1996   1997-01-07T19:29:28Z!djm@gnu.org
+gcc-2_8_1-980401          1998-02-13T12:16:46Z!kenner@gnu.org
+gcc-2_8_1-980402          1998-04-27T23:48:59Z!drepper@redhat.com
+gcc-2_8_1-980407          1998-02-13T12:16:46Z!kenner@gnu.org
+gcc-2_8_1-980412          1998-02-13T12:16:46Z!kenner@gnu.org
+gcc-2_8_1-980413          1998-02-13T12:16:46Z!kenner@gnu.org
+gcc-2_8_1-980419          1998-04-14T00:02:53Z!drepper@redhat.com
+gcc-2_8_1-980426          1998-04-14T00:02:53Z!drepper@redhat.com
+gcc-2_8_1-980502          1998-04-27T23:48:59Z!drepper@redhat.com
+gcc-2_8_1-980513          1998-04-27T23:48:59Z!drepper@redhat.com
+gcc-2_8_1-980525          1998-05-19T07:09:32Z!drepper@redhat.com
+gcc-2_8_1-980529          1998-05-19T07:09:32Z!drepper@redhat.com
+gcc-2_8_1-980608          1998-05-19T07:09:32Z!drepper@redhat.com
+gcc-2_8_1-980609          1998-05-19T07:09:32Z!drepper@redhat.com
+gcc-2_8_1-980627          1998-06-13T19:51:10Z!kenner@gnu.org
+gcc-2_8_1-980705          1998-06-13T19:51:10Z!kenner@gnu.org
+gcc-2_8_1-980718          1998-06-13T19:51:10Z!kenner@gnu.org
+gcc-2_8_1-980811          1998-08-09T22:42:36Z!rms@gnu.org
+gcc-2_8_1-980813          1998-08-12T21:32:31Z!rms@gnu.org
+gcc-2_8_1-980928          1998-09-28T11:03:36Z!bje@air.net.au
+gcc-2_8_1-980929          1998-09-28T11:03:36Z!bje@air.net.au
+gcc-2_8_1-RELEASE         1998-02-13T12:16:46Z!kenner@gnu.org
+gcc_2_8_1-980315          1998-02-13T12:16:46Z!kenner@gnu.org
+gcc_2_8_1-980929          1998-09-28T11:03:36Z!bje@air.net.au
+glibc-2_0_2               1997-01-07T19:29:28Z!djm@gnu.org
+gnumach-release-1-1       1997-05-07T19:19:04Z!Thomas
+gnumach-release-1-1-1     1997-05-07T19:19:04Z!Thomas
+gnumach-release-1-1-2     1997-06-10T04:18:36Z!rms@gnu.org
+gnumach-release-1-1-3     1997-06-10T04:18:36Z!rms@gnu.org
+hurd-release-0-2          1997-06-10T04:18:36Z!rms@gnu.org
+jimb-sync-Nov-3-1992      1992-11-07T05:29:26Z!jimb@redhat.com
+libc20x-97031             1997-01-07T19:29:28Z!djm@gnu.org
+libc20x-970306            1997-01-07T19:29:28Z!djm@gnu.org
+libc20x-970316            1997-01-07T19:29:28Z!djm@gnu.org
+libc20x-970318            1997-01-07T19:29:28Z!djm@gnu.org
+libc20x-970319            1997-01-07T19:29:28Z!djm@gnu.org
+libc20x-970404            1997-01-07T19:29:28Z!djm@gnu.org
+libc-1-90                 1996-06-08T01:25:20Z!bothner@cygnus.com
+libc-1-91                 1996-06-18T18:23:57Z!ian@cygnus.com
+libc-1-92                 1996-06-20T16:20:05Z!gnu@the-meissners.org
+libc-1-93                 1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-950402               1995-03-22T08:54:39Z!rms@gnu.org
+libc-950411               1995-04-07T07:32:44Z!rms@gnu.org
+libc-950722               1995-06-28T21:57:23Z!kenner@gnu.org
+libc-950723               1995-06-28T21:57:23Z!kenner@gnu.org
+libc-950922               1995-08-15T02:33:42Z!bothner@cygnus.com
+libc-951016               1995-08-15T02:33:42Z!bothner@cygnus.com
+libc-951018               1995-10-16T15:40:29Z!law@redhat.com
+libc-951029               1995-10-16T15:40:29Z!law@redhat.com
+libc-951031               1995-10-16T15:40:29Z!law@redhat.com
+libc-951101               1995-10-16T15:40:29Z!law@redhat.com
+libc-951102               1995-10-16T15:40:29Z!law@redhat.com
+libc-951103               1995-10-16T15:40:29Z!law@redhat.com
+libc-951104               1995-10-16T15:40:29Z!law@redhat.com
+libc-951105               1995-10-16T15:40:29Z!law@redhat.com
+libc-951106               1995-10-16T15:40:29Z!law@redhat.com
+libc-951107               1995-10-16T15:40:29Z!law@redhat.com
+libc-951108               1995-10-16T15:40:29Z!law@redhat.com
+libc-951109               1995-10-16T15:40:29Z!law@redhat.com
+libc-951110               1995-10-16T15:40:29Z!law@redhat.com
+libc-951111               1995-10-16T15:40:29Z!law@redhat.com
+libc-951112               1995-10-16T15:40:29Z!law@redhat.com
+libc-951113               1995-10-16T15:40:29Z!law@redhat.com
+libc-951114               1995-10-16T15:40:29Z!law@redhat.com
+libc-951115               1995-10-16T15:40:29Z!law@redhat.com
+libc-951116               1995-10-16T15:40:29Z!law@redhat.com
+libc-951117               1995-10-16T15:40:29Z!law@redhat.com
+libc-951118               1995-10-16T15:40:29Z!law@redhat.com
+libc-951119               1995-10-16T15:40:29Z!law@redhat.com
+libc-951120               1995-10-16T15:40:29Z!law@redhat.com
+libc-951121               1995-10-16T15:40:29Z!law@redhat.com
+libc-951122               1995-10-16T15:40:29Z!law@redhat.com
+libc-951123               1995-10-16T15:40:29Z!law@redhat.com
+libc-951124               1995-10-16T15:40:29Z!law@redhat.com
+libc-951125               1995-10-16T15:40:29Z!law@redhat.com
+libc-951126               1995-10-16T15:40:29Z!law@redhat.com
+libc-951127               1995-10-16T15:40:29Z!law@redhat.com
+libc-951128               1995-10-16T15:40:29Z!law@redhat.com
+libc-951129               1995-10-16T15:40:29Z!law@redhat.com
+libc-951130               1995-10-16T15:40:29Z!law@redhat.com
+libc-951201               1995-11-30T21:59:48Z!bothner@cygnus.com
+libc-951202               1995-11-30T21:59:48Z!bothner@cygnus.com
+libc-951203               1995-11-30T21:59:48Z!bothner@cygnus.com
+libc-951204               1995-11-30T21:59:48Z!bothner@cygnus.com
+libc-951206               1995-12-04T18:22:22Z!law@redhat.com
+libc-951208               1995-12-06T11:57:46Z!erich@uruk.org
+libc-951209               1995-12-06T11:57:46Z!erich@uruk.org
+libc-951210               1995-12-06T11:57:46Z!erich@uruk.org
+libc-951211               1995-12-06T11:57:46Z!erich@uruk.org
+libc-951212               1995-12-12T00:47:21Z!bothner@cygnus.com
+libc-951213               1995-12-12T00:47:21Z!bothner@cygnus.com
+libc-951214               1995-12-13T21:43:08Z!ian@cygnus.com
+libc-951215               1995-12-13T21:43:08Z!ian@cygnus.com
+libc-951216               1995-12-16T03:32:35Z!scox@redhat.com
+libc-951217               1995-12-16T03:32:35Z!scox@redhat.com
+libc-951218               1995-12-16T03:32:35Z!scox@redhat.com
+libc-951219               1995-12-16T03:32:35Z!scox@redhat.com
+libc-951220               1995-12-16T03:32:35Z!scox@redhat.com
+libc-951221               1995-12-16T03:32:35Z!scox@redhat.com
+libc-951222               1995-12-16T03:32:35Z!scox@redhat.com
+libc-951223               1995-12-16T03:32:35Z!scox@redhat.com
+libc-951224               1995-12-16T03:32:35Z!scox@redhat.com
+libc-951225               1995-12-16T03:32:35Z!scox@redhat.com
+libc-951226               1995-12-16T03:32:35Z!scox@redhat.com
+libc-951227               1995-12-16T03:32:35Z!scox@redhat.com
+libc-951228               1995-12-16T03:32:35Z!scox@redhat.com
+libc-951229               1995-12-16T03:32:35Z!scox@redhat.com
+libc-951230               1995-12-16T03:32:35Z!scox@redhat.com
+libc-951231               1995-12-16T03:32:35Z!scox@redhat.com
+libc-960101               1995-12-16T03:32:35Z!scox@redhat.com
+libc-960102               1995-12-16T03:32:35Z!scox@redhat.com
+libc-960103               1995-12-16T03:32:35Z!scox@redhat.com
+libc-960104               1995-12-16T03:32:35Z!scox@redhat.com
+libc-960105               1995-12-16T03:32:35Z!scox@redhat.com
+libc-960106               1995-12-16T03:32:35Z!scox@redhat.com
+libc-960107               1995-12-16T03:32:35Z!scox@redhat.com
+libc-960108               1995-12-16T03:32:35Z!scox@redhat.com
+libc-960109               1995-12-16T03:32:35Z!scox@redhat.com
+libc-960110               1995-12-16T03:32:35Z!scox@redhat.com
+libc-960111               1995-12-16T03:32:35Z!scox@redhat.com
+libc-960112               1995-12-16T03:32:35Z!scox@redhat.com
+libc-960113               1995-12-16T03:32:35Z!scox@redhat.com
+libc-960114               1995-12-16T03:32:35Z!scox@redhat.com
+libc-960115               1995-12-16T03:32:35Z!scox@redhat.com
+libc-960116               1996-01-16T01:58:43Z!kenner@gnu.org
+libc-960117               1996-01-16T01:58:43Z!kenner@gnu.org
+libc-960118               1996-01-17T23:54:58Z!dje@gnu.org
+libc-960119               1996-01-17T23:54:58Z!dje@gnu.org
+libc-960120               1996-01-17T23:54:58Z!dje@gnu.org
+libc-960121               1996-01-17T23:54:58Z!dje@gnu.org
+libc-960122               1996-01-17T23:54:58Z!dje@gnu.org
+libc-960123               1996-01-17T23:54:58Z!dje@gnu.org
+libc-960124               1996-01-17T23:54:58Z!dje@gnu.org
+libc-960125               1996-01-17T23:54:58Z!dje@gnu.org
+libc-960126               1996-01-17T23:54:58Z!dje@gnu.org
+libc-960127               1996-01-17T23:54:58Z!dje@gnu.org
+libc-960128               1996-01-17T23:54:58Z!dje@gnu.org
+libc-960129               1996-01-17T23:54:58Z!dje@gnu.org
+libc-960130               1996-01-17T23:54:58Z!dje@gnu.org
+libc-960131               1996-01-17T23:54:58Z!dje@gnu.org
+libc-960201               1996-01-31T19:14:05Z!ian@cygnus.com
+libc-960202               1996-01-31T19:14:05Z!ian@cygnus.com
+libc-960203               1996-02-03T01:03:27Z!gnu@the-meissners.org
+libc-960204               1996-02-03T01:03:27Z!gnu@the-meissners.org
+libc-960205               1996-02-03T01:03:27Z!gnu@the-meissners.org
+libc-960206               1996-02-03T01:03:27Z!gnu@the-meissners.org
+libc-960207               1996-02-03T01:03:27Z!gnu@the-meissners.org
+libc-960208               1996-02-03T01:03:27Z!gnu@the-meissners.org
+libc-960209               1996-02-03T01:03:27Z!gnu@the-meissners.org
+libc-960210               1996-02-03T01:03:27Z!gnu@the-meissners.org
+libc-960211               1996-02-10T13:26:26Z!kenner@gnu.org
+libc-960212               1996-02-11T23:40:37Z!rms@gnu.org
+libc-960213               1996-02-12T23:15:30Z!dje@gnu.org
+libc-960214               1996-02-12T23:15:30Z!dje@gnu.org
+libc-960215               1996-02-12T23:15:30Z!dje@gnu.org
+libc-960216               1996-02-12T23:15:30Z!dje@gnu.org
+libc-960217               1996-02-12T23:15:30Z!dje@gnu.org
+libc-960218               1996-02-12T23:15:30Z!dje@gnu.org
+libc-960219               1996-02-12T23:15:30Z!dje@gnu.org
+libc-960220               1996-02-12T23:15:30Z!dje@gnu.org
+libc-960221               1996-02-12T23:15:30Z!dje@gnu.org
+libc-960222               1996-02-12T23:15:30Z!dje@gnu.org
+libc-960223               1996-02-12T23:15:30Z!dje@gnu.org
+libc-960224               1996-02-12T23:15:30Z!dje@gnu.org
+libc-960225               1996-02-12T23:15:30Z!dje@gnu.org
+libc-960226               1996-02-12T23:15:30Z!dje@gnu.org
+libc-960227               1996-02-12T23:15:30Z!dje@gnu.org
+libc-960228               1996-02-12T23:15:30Z!dje@gnu.org
+libc-960229               1996-02-12T23:15:30Z!dje@gnu.org
+libc-960302               1996-03-01T14:57:49Z!roland@gnu.org
+libc-960303               1996-03-01T14:57:49Z!roland@gnu.org
+libc-960304               1996-03-01T14:57:49Z!roland@gnu.org
+libc-960305               1996-03-05T03:02:45Z!erik@naggum.no
+libc-960306               1996-03-05T23:34:58Z!kenner@gnu.org
+libc-960307               1996-03-05T23:34:58Z!kenner@gnu.org
+libc-960308               1996-03-05T23:34:58Z!kenner@gnu.org
+libc-960309               1996-03-05T23:34:58Z!kenner@gnu.org
+libc-960310               1996-03-05T23:34:58Z!kenner@gnu.org
+libc-960311               1996-03-05T23:34:58Z!kenner@gnu.org
+libc-960312               1996-03-05T23:34:58Z!kenner@gnu.org
+libc-960313               1996-03-05T23:34:58Z!kenner@gnu.org
+libc-960314               1996-03-05T23:34:58Z!kenner@gnu.org
+libc-960315               1996-03-15T00:14:04Z!ian@cygnus.com
+libc-960316               1996-03-15T00:14:04Z!ian@cygnus.com
+libc-960317               1996-03-15T00:14:04Z!ian@cygnus.com
+libc-960318               1996-03-15T00:14:04Z!ian@cygnus.com
+libc-960319               1996-03-15T00:14:04Z!ian@cygnus.com
+libc-960320               1996-03-15T00:14:04Z!ian@cygnus.com
+libc-960321               1996-03-15T00:14:04Z!ian@cygnus.com
+libc-960322               1996-03-21T23:26:26Z!dje@gnu.org
+libc-960323               1996-03-21T23:26:26Z!dje@gnu.org
+libc-960324               1996-03-21T23:26:26Z!dje@gnu.org
+libc-960325               1996-03-21T23:26:26Z!dje@gnu.org
+libc-960326               1996-03-21T23:26:26Z!dje@gnu.org
+libc-960327               1996-03-21T23:26:26Z!dje@gnu.org
+libc-960328               1996-03-21T23:26:26Z!dje@gnu.org
+libc-960329               1996-03-29T01:49:55Z!dje@gnu.org
+libc-960330               1996-03-29T01:49:55Z!dje@gnu.org
+libc-960331               1996-03-29T01:49:55Z!dje@gnu.org
+libc-960401               1996-03-29T01:49:55Z!dje@gnu.org
+libc-960402               1996-03-29T01:49:55Z!dje@gnu.org
+libc-960403               1996-03-29T01:49:55Z!dje@gnu.org
+libc-960404               1996-03-29T01:49:55Z!dje@gnu.org
+libc-960405               1996-03-29T01:49:55Z!dje@gnu.org
+libc-960406               1996-03-29T01:49:55Z!dje@gnu.org
+libc-960407               1996-03-29T01:49:55Z!dje@gnu.org
+libc-960408               1996-03-29T01:49:55Z!dje@gnu.org
+libc-960409               1996-04-08T20:19:10Z!gnu@the-meissners.org
+libc-960410               1996-04-08T20:19:10Z!gnu@the-meissners.org
+libc-960411               1996-04-08T20:19:10Z!gnu@the-meissners.org
+libc-960412               1996-04-08T20:19:10Z!gnu@the-meissners.org
+libc-960413               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960414               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960415               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960416               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960417               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960418               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960419               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960420               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960421               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960422               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960423               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960424               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960425               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960426               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960427               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960428               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960429               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960430               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960501               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960502               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960503               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960504               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960505               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960506               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960507               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960508               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960509               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960510               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960511               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960512               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960513               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960514               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960515               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960516               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960517               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960518               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960519               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960520               1996-04-13T00:06:54Z!bothner@cygnus.com
+libc-960521               1996-05-20T16:02:45Z!law@redhat.com
+libc-960522               1996-05-21T22:55:56Z!roland@gnu.org
+libc-960523               1996-05-21T22:55:56Z!roland@gnu.org
+libc-960524               1996-05-21T22:55:56Z!roland@gnu.org
+libc-960525               1996-05-24T22:34:49Z!roland@gnu.org
+libc-960526               1996-05-24T22:34:49Z!roland@gnu.org
+libc-960527               1996-05-24T22:34:49Z!roland@gnu.org
+libc-960528               1996-05-24T22:34:49Z!roland@gnu.org
+libc-960529               1996-05-24T22:34:49Z!roland@gnu.org
+libc-960530               1996-05-24T22:34:49Z!roland@gnu.org
+libc-960531               1996-05-24T22:34:49Z!roland@gnu.org
+libc-960601               1996-05-24T22:34:49Z!roland@gnu.org
+libc-960602               1996-05-24T22:34:49Z!roland@gnu.org
+libc-960603               1996-05-24T22:34:49Z!roland@gnu.org
+libc-960604               1996-06-03T12:51:33Z!kwzh@gnu.org
+libc-960605               1996-06-05T04:12:46Z!bothner@cygnus.com
+libc-960606               1996-06-05T04:12:46Z!bothner@cygnus.com
+libc-960607               1996-06-05T04:12:46Z!bothner@cygnus.com
+libc-960608               1996-06-08T01:25:20Z!bothner@cygnus.com
+libc-960609               1996-06-08T01:25:20Z!bothner@cygnus.com
+libc-960610               1996-06-08T01:25:20Z!bothner@cygnus.com
+libc-960611               1996-06-08T01:25:20Z!bothner@cygnus.com
+libc-960612               1996-06-08T01:25:20Z!bothner@cygnus.com
+libc-960613               1996-06-08T01:25:20Z!bothner@cygnus.com
+libc-960614               1996-06-08T01:25:20Z!bothner@cygnus.com
+libc-960615               1996-06-08T01:25:20Z!bothner@cygnus.com
+libc-960616               1996-06-08T01:25:20Z!bothner@cygnus.com
+libc-960617               1996-06-08T01:25:20Z!bothner@cygnus.com
+libc-960618               1996-06-08T01:25:20Z!bothner@cygnus.com
+libc-960619               1996-06-18T18:23:57Z!ian@cygnus.com
+libc-960620               1996-06-18T18:23:57Z!ian@cygnus.com
+libc-960621               1996-06-20T16:20:05Z!gnu@the-meissners.org
+libc-960622               1996-06-20T16:20:05Z!gnu@the-meissners.org
+libc-960623               1996-06-20T16:20:05Z!gnu@the-meissners.org
+libc-960624               1996-06-20T16:20:05Z!gnu@the-meissners.org
+libc-960625               1996-06-20T16:20:05Z!gnu@the-meissners.org
+libc-960626               1996-06-20T16:20:05Z!gnu@the-meissners.org
+libc-960627               1996-06-20T16:20:05Z!gnu@the-meissners.org
+libc-960628               1996-06-20T16:20:05Z!gnu@the-meissners.org
+libc-960629               1996-06-28T17:28:58Z!kenner@gnu.org
+libc-960630               1996-06-28T17:28:58Z!kenner@gnu.org
+libc-960701               1996-06-28T17:28:58Z!kenner@gnu.org
+libc-960702               1996-06-28T17:28:58Z!kenner@gnu.org
+libc-960703               1996-06-28T17:28:58Z!kenner@gnu.org
+libc-960704               1996-06-28T17:28:58Z!kenner@gnu.org
+libc-960705               1996-06-28T17:28:58Z!kenner@gnu.org
+libc-960706               1996-06-28T17:28:58Z!kenner@gnu.org
+libc-960707               1996-06-28T17:28:58Z!kenner@gnu.org
+libc-960708               1996-07-07T17:26:50Z!dje@gnu.org
+libc-960709               1996-07-07T17:26:50Z!dje@gnu.org
+libc-960710               1996-07-07T17:26:50Z!dje@gnu.org
+libc-960711               1996-07-07T17:26:50Z!dje@gnu.org
+libc-960712               1996-07-07T17:26:50Z!dje@gnu.org
+libc-960713               1996-07-07T17:26:50Z!dje@gnu.org
+libc-960714               1996-07-07T17:26:50Z!dje@gnu.org
+libc-960715               1996-07-14T18:09:15Z!tege@swox.com
+libc-960716               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960717               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960718               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960719               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960720               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960721               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960722               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960723               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960724               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960725               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960726               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960727               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960728               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960729               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960730               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960731               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960801               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960802               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960803               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960804               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960805               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960806               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960807               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960808               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960809               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960810               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960811               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960812               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960813               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960814               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960815               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960816               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960817               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960818               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960819               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960820               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960821               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960822               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960823               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960824               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960825               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960826               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960827               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960828               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960829               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960830               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960831               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960901               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960902               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960903               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960904               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960905               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960906               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960907               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960908               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960909               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960910               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960911               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960912               1996-07-16T04:47:46Z!kwzh@gnu.org
+libc-960913               1996-09-13T03:46:14Z!rms@gnu.org
+libc-960918               1996-09-15T00:49:22Z!kenner@gnu.org
+libc-960919               1996-09-15T00:49:22Z!kenner@gnu.org
+libc-960920               1996-09-15T00:49:22Z!kenner@gnu.org
+libc-960921               1996-09-15T00:49:22Z!kenner@gnu.org
+libc-960922               1996-09-15T00:49:22Z!kenner@gnu.org
+libc-960923               1996-09-15T00:49:22Z!kenner@gnu.org
+libc-960925               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-960926               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-960927               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-960928               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-960929               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961001               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961004               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961005               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961006               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961007               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961008               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961009               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961010               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961011               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961012               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961013               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961014               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961015               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961016               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961017               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961018               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961019               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961020               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961021               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961022               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961023               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961024               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961025               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961026               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961027               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961028               1996-09-24T02:44:17Z!kenner@gnu.org
+libc-961029               1996-10-29T02:56:12Z!rms@gnu.org
+libc-961030               1996-10-29T02:56:12Z!rms@gnu.org
+libc-961031               1996-10-29T02:56:12Z!rms@gnu.org
+libc-961101               1996-10-29T02:56:12Z!rms@gnu.org
+libc-961102               1996-10-29T02:56:12Z!rms@gnu.org
+libc-961103               1996-10-29T02:56:12Z!rms@gnu.org
+libc-961104               1996-10-29T02:56:12Z!rms@gnu.org
+libc-961105               1996-10-29T02:56:12Z!rms@gnu.org
+libc-961106               1996-10-29T02:56:12Z!rms@gnu.org
+libc-961107               1996-10-29T02:56:12Z!rms@gnu.org
+libc-961108               1996-11-08T07:35:31Z!djm@gnu.org
+libc-961109               1996-11-08T07:35:31Z!djm@gnu.org
+libc-961110               1996-11-08T07:35:31Z!djm@gnu.org
+libc-961111               1996-11-08T07:35:31Z!djm@gnu.org
+libc-961114               1996-11-14T02:06:05Z!bothner@cygnus.com
+libc-961115               1996-11-14T02:06:05Z!bothner@cygnus.com
+libc-961116               1996-11-14T02:06:05Z!bothner@cygnus.com
+libc-961117               1996-11-14T02:06:05Z!bothner@cygnus.com
+libc-961118               1996-11-14T02:06:05Z!bothner@cygnus.com
+libc-961119               1996-11-14T02:06:05Z!bothner@cygnus.com
+libc-961120               1996-11-19T18:40:34Z!djm@gnu.org
+libc-961121               1996-11-20T21:28:32Z!djm@gnu.org
+libc-961203               1996-11-21T22:20:09Z!Thomas
+libc-961204               1996-11-21T22:20:09Z!Thomas
+libc-961205               1996-11-21T22:20:09Z!Thomas
+libc-961206               1996-11-21T22:20:09Z!Thomas
+libc-961207               1996-11-21T22:20:09Z!Thomas
+libc-961208               1996-12-07T22:47:59Z!kenner@gnu.org
+libc-961209               1996-12-07T22:47:59Z!kenner@gnu.org
+libc-961210               1996-12-07T22:47:59Z!kenner@gnu.org
+libc-961211               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961212               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961213               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961214               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961215               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961216               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961217               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961218               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961219               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961220               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961221               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961222               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961223               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961224               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961225               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961226               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961227               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961228               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961229               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961230               1996-12-11T00:37:52Z!djm@gnu.org
+libc-961231               1996-12-11T00:37:52Z!djm@gnu.org
+libc-970101               1996-12-31T20:54:33Z!ian@cygnus.com
+libc-970102               1996-12-31T20:54:33Z!ian@cygnus.com
+libc-970103               1996-12-31T20:54:33Z!ian@cygnus.com
+libc-970104               1997-01-03T13:38:47Z!kenner@gnu.org
+libc-970105               1997-01-05T03:44:26Z!miles@gnu.org
+libc-970106               1997-01-05T03:44:26Z!miles@gnu.org
+libc-970107               1997-01-05T03:44:26Z!miles@gnu.org
+libc-970108               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970109               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970110               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970111               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970112               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970113               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970114               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970115               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970116               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970117               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970118               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970119               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970120               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970121               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970122               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970123               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970124               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970125               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970126               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970127               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970128               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970129               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970130               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970131               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970201               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970202               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970203               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970204               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970205               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970206               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970207               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970208               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970209               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970210               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970211               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970212               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970213               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970214               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970215               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970216               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970217               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970218               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970219               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970220               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970221               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970222               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970223               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970224               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970225               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970226               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970227               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970228               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970301               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970302               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970303               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970304               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970305               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970306               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970307               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970308               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970309               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970310               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970311               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970312               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970313               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970314               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970315               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970316               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970317               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970318               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970319               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970320               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970321               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970322               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970323               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970324               1997-01-07T19:29:28Z!djm@gnu.org
+libc-970325               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970326               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970327               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970328               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970329               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970330               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970331               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970401               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970402               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970403               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970404               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970405               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970406               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970407               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970408               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970409               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970410               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970411               1997-03-24T20:38:28Z!dje@gnu.org
+libc-970412               1997-04-11T20:40:28Z!ian@cygnus.com
+libc-970413               1997-04-11T20:40:28Z!ian@cygnus.com
+libc-970414               1997-04-11T20:40:28Z!ian@cygnus.com
+libc-970415               1997-04-11T20:40:28Z!ian@cygnus.com
+libc-970416               1997-04-11T20:40:28Z!ian@cygnus.com
+libc-970417               1997-04-11T20:40:28Z!ian@cygnus.com
+libc-970418               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970419               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970420               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970421               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970422               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970423               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970424               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970425               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970426               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970427               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970428               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970429               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970430               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970501               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970502               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970503               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970504               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970505               1997-04-17T18:00:12Z!ian@cygnus.com
+libc-970506               1997-05-05T22:04:41Z!bothner@cygnus.com
+libc-970507               1997-05-05T22:04:41Z!bothner@cygnus.com
+libc-970508               1997-05-07T19:19:04Z!Thomas
+libc-970509               1997-05-07T19:19:04Z!Thomas
+libc-970510               1997-05-07T19:19:04Z!Thomas
+libc-970511               1997-05-07T19:19:04Z!Thomas
+libc-970512               1997-05-07T19:19:04Z!Thomas
+libc-970513               1997-05-07T19:19:04Z!Thomas
+libc-970514               1997-05-07T19:19:04Z!Thomas
+libc-970515               1997-05-07T19:19:04Z!Thomas
+libc-970516               1997-05-07T19:19:04Z!Thomas
+libc-970517               1997-05-07T19:19:04Z!Thomas
+libc-970518               1997-05-07T19:19:04Z!Thomas
+libc-970519               1997-05-07T19:19:04Z!Thomas
+libc-970520               1997-05-07T19:19:04Z!Thomas
+libc-970521               1997-05-07T19:19:04Z!Thomas
+libc-970522               1997-05-07T19:19:04Z!Thomas
+libc-970523               1997-05-07T19:19:04Z!Thomas
+libc-970524               1997-05-07T19:19:04Z!Thomas
+libc-970525               1997-05-07T19:19:04Z!Thomas
+libc-970526               1997-05-07T19:19:04Z!Thomas
+libc-970527               1997-05-07T19:19:04Z!Thomas
+libc-970528               1997-05-07T19:19:04Z!Thomas
+libc-970529               1997-05-07T19:19:04Z!Thomas
+libc-970530               1997-05-07T19:19:04Z!Thomas
+libc-970531               1997-05-07T19:19:04Z!Thomas
+libc-970601               1997-05-07T19:19:04Z!Thomas
+libc-970602               1997-05-07T19:19:04Z!Thomas
+libc-970603               1997-05-07T19:19:04Z!Thomas
+libc-970604               1997-05-07T19:19:04Z!Thomas
+libc-970605               1997-05-07T19:19:04Z!Thomas
+libc-970606               1997-06-06T01:21:12Z!rms@gnu.org
+libc-970607               1997-06-06T01:21:12Z!rms@gnu.org
+libc-970608               1997-06-08T01:57:13Z!rms@gnu.org
+libc-970609               1997-06-09T04:56:02Z!rms@gnu.org
+libc-970610               1997-06-10T04:18:36Z!rms@gnu.org
+libc-970611               1997-06-10T04:18:36Z!rms@gnu.org
+libc-970612               1997-06-10T04:18:36Z!rms@gnu.org
+libc-970613               1997-06-10T04:18:36Z!rms@gnu.org
+libc-970614               1997-06-10T04:18:36Z!rms@gnu.org
+libc-970615               1997-06-10T04:18:36Z!rms@gnu.org
+libc-970616               1997-06-10T04:18:36Z!rms@gnu.org
+libc-970617               1997-06-10T04:18:36Z!rms@gnu.org
+libc-970618               1997-06-10T04:18:36Z!rms@gnu.org
+libc-970619               1997-06-10T04:18:36Z!rms@gnu.org
+libc-970620               1997-06-10T04:18:36Z!rms@gnu.org
+libc-970621               1997-06-10T04:18:36Z!rms@gnu.org
+libc-970622               1997-06-10T04:18:36Z!rms@gnu.org
+libc-970624               1997-06-23T17:53:11Z!law@redhat.com
+libc-970625               1997-06-23T17:53:11Z!law@redhat.com
+libc-970626               1997-06-23T17:53:11Z!law@redhat.com
+libc-970627               1997-06-23T17:53:11Z!law@redhat.com
+libc-970628               1997-06-27T19:20:14Z!kenner@gnu.org
+libc-970629               1997-06-27T19:20:14Z!kenner@gnu.org
+libc-970630               1997-06-27T19:20:14Z!kenner@gnu.org
+libc-970701               1997-06-27T19:20:14Z!kenner@gnu.org
+libc-970702               1997-06-27T19:20:14Z!kenner@gnu.org
+libc-970703               1997-06-27T19:20:14Z!kenner@gnu.org
+libc-970704               1997-06-27T19:20:14Z!kenner@gnu.org
+libc-970705               1997-06-27T19:20:14Z!kenner@gnu.org
+libc-970707               1997-07-07T08:40:20Z!rms@gnu.org
+libc-970708               1997-07-07T08:40:20Z!rms@gnu.org
+libc-970709               1997-07-07T08:40:20Z!rms@gnu.org
+libc-970710               1997-07-07T08:40:20Z!rms@gnu.org
+libc-970713               1997-07-07T08:40:20Z!rms@gnu.org
+libc-970715               1997-07-14T19:53:44Z!rms@gnu.org
+libc-970717               1997-07-16T14:45:30Z!erich@uruk.org
+libc-970718               1997-07-16T14:45:30Z!erich@uruk.org
+libc-970719               1997-07-16T14:45:30Z!erich@uruk.org
+libc-970720               1997-07-16T14:45:30Z!erich@uruk.org
+libc-970721               1997-07-21T00:58:41Z!kenner@gnu.org
+libc-970722               1997-07-21T00:58:41Z!kenner@gnu.org
+libc-970723               1997-07-21T00:58:41Z!kenner@gnu.org
+libc-970724               1997-07-21T00:58:41Z!kenner@gnu.org
+libc-970725               1997-07-21T00:58:41Z!kenner@gnu.org
+libc-970726               1997-07-21T00:58:41Z!kenner@gnu.org
+libc-970727               1997-07-26T19:01:01Z!bothner@cygnus.com
+libc-970728               1997-07-26T19:01:01Z!bothner@cygnus.com
+libc-970729               1997-07-28T23:37:45Z!drepper@redhat.com
+libc-970730               1997-07-28T23:37:45Z!drepper@redhat.com
+libc-970731               1997-07-28T23:37:45Z!drepper@redhat.com
+libc-970801               1997-07-28T23:37:45Z!drepper@redhat.com
+libc-970802               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970803               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970804               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970805               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970806               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970807               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970808               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970809               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970810               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970811               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970812               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970813               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970814               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970815               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970816               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970817               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970818               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970819               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970820               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970821               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970822               1997-08-01T18:09:30Z!rms@gnu.org
+libc-970823               1997-08-22T14:49:11Z!law@redhat.com
+libc-970824               1997-08-22T14:49:11Z!law@redhat.com
+libc-970825               1997-08-22T14:49:11Z!law@redhat.com
+libc-970826               1997-08-22T14:49:11Z!law@redhat.com
+libc-970827               1997-08-26T09:21:29Z!kenner@gnu.org
+libc-970828               1997-08-26T09:21:29Z!kenner@gnu.org
+libc-970829               1997-08-26T09:21:29Z!kenner@gnu.org
+libc-970830               1997-08-26T09:21:29Z!kenner@gnu.org
+libc-970831               1997-08-26T09:21:29Z!kenner@gnu.org
+libc-970901               1997-08-26T09:21:29Z!kenner@gnu.org
+libc-970902               1997-08-26T09:21:29Z!kenner@gnu.org
+libc-970903               1997-08-26T09:21:29Z!kenner@gnu.org
+libc-970904               1997-08-26T09:21:29Z!kenner@gnu.org
+libc-970905               1997-08-26T09:21:29Z!kenner@gnu.org
+libc-970906               1997-09-05T18:08:34Z!law@redhat.com
+libc-970907               1997-09-05T18:08:34Z!law@redhat.com
+libc-970908               1997-09-05T18:08:34Z!law@redhat.com
+libc-970911               1997-09-10T21:16:20Z!law@redhat.com
+libc-970912               1997-09-10T21:16:20Z!law@redhat.com
+libc-970913               1997-09-10T21:16:20Z!law@redhat.com
+libc-970914               1997-09-10T21:16:20Z!law@redhat.com
+libc-970915               1997-09-10T21:16:20Z!law@redhat.com
+libc-970916               1997-09-10T21:16:20Z!law@redhat.com
+libc-970917               1997-09-10T21:16:20Z!law@redhat.com
+libc-970918               1997-09-10T21:16:20Z!law@redhat.com
+libc-970919               1997-09-10T21:16:20Z!law@redhat.com
+libc-970920               1997-09-10T21:16:20Z!law@redhat.com
+libc-970921               1997-09-10T21:16:20Z!law@redhat.com
+libc-970922               1997-09-10T21:16:20Z!law@redhat.com
+libc-970923               1997-09-10T21:16:20Z!law@redhat.com
+libc-970924               1997-09-10T21:16:20Z!law@redhat.com
+libc-970925               1997-09-10T21:16:20Z!law@redhat.com
+libc-970926               1997-09-10T21:16:20Z!law@redhat.com
+libc-970927               1997-09-10T21:16:20Z!law@redhat.com
+libc-970928               1997-09-10T21:16:20Z!law@redhat.com
+libc-970929               1997-09-10T21:16:20Z!law@redhat.com
+libc-970930               1997-09-10T21:16:20Z!law@redhat.com
+libc-971001               1997-09-10T21:16:20Z!law@redhat.com
+libc-971018               1997-09-10T21:16:20Z!law@redhat.com
+libc-971019               1997-09-10T21:16:20Z!law@redhat.com
+libc-971020               1997-09-10T21:16:20Z!law@redhat.com
+libc-971021               1997-09-10T21:16:20Z!law@redhat.com
+libc-971022               1997-09-10T21:16:20Z!law@redhat.com
+libc-971023               1997-09-10T21:16:20Z!law@redhat.com
+libc-971024               1997-09-10T21:16:20Z!law@redhat.com
+libc-971025               1997-09-10T21:16:20Z!law@redhat.com
+libc-971026               1997-09-10T21:16:20Z!law@redhat.com
+libc-971027               1997-09-10T21:16:20Z!law@redhat.com
+libc-971028               1997-09-10T21:16:20Z!law@redhat.com
+libc-971029               1997-09-10T21:16:20Z!law@redhat.com
+libc-971030               1997-09-10T21:16:20Z!law@redhat.com
+libc-971031               1997-09-10T21:16:20Z!law@redhat.com
+libc-971101               1997-09-10T21:16:20Z!law@redhat.com
+libc-971102               1997-09-10T21:16:20Z!law@redhat.com
+libc-971103               1997-09-10T21:16:20Z!law@redhat.com
+libc-971104               1997-09-10T21:16:20Z!law@redhat.com
+libc-971105               1997-09-10T21:16:20Z!law@redhat.com
+libc-971106               1997-09-10T21:16:20Z!law@redhat.com
+libc-971107               1997-09-10T21:16:20Z!law@redhat.com
+libc-971108               1997-09-10T21:16:20Z!law@redhat.com
+libc-971109               1997-09-10T21:16:20Z!law@redhat.com
+libc-971110               1997-09-10T21:16:20Z!law@redhat.com
+libc-971111               1997-09-10T21:16:20Z!law@redhat.com
+libc-971112               1997-09-10T21:16:20Z!law@redhat.com
+libc-971113               1997-09-10T21:16:20Z!law@redhat.com
+libc-971114               1997-09-10T21:16:20Z!law@redhat.com
+libc-971115               1997-09-10T21:16:20Z!law@redhat.com
+libc-971116               1997-09-10T21:16:20Z!law@redhat.com
+libc-971117               1997-09-10T21:16:20Z!law@redhat.com
+libc-971118               1997-09-10T21:16:20Z!law@redhat.com
+libc-971120               1997-09-10T21:16:20Z!law@redhat.com
+libc-971121               1997-09-10T21:16:20Z!law@redhat.com
+libc-971122               1997-09-10T21:16:20Z!law@redhat.com
+libc-971123               1997-09-10T21:16:20Z!law@redhat.com
+libc-971124               1997-09-10T21:16:20Z!law@redhat.com
+libc-971125               1997-09-10T21:16:20Z!law@redhat.com
+libc-971126               1997-09-10T21:16:20Z!law@redhat.com
+libc-971127               1997-09-10T21:16:20Z!law@redhat.com
+libc-971128               1997-09-10T21:16:20Z!law@redhat.com
+libc-971129               1997-09-10T21:16:20Z!law@redhat.com
+libc-971130               1997-09-10T21:16:20Z!law@redhat.com
+libc-971201               1997-09-10T21:16:20Z!law@redhat.com
+libc-971203               1997-09-10T21:16:20Z!law@redhat.com
+libc-971204               1997-09-10T21:16:20Z!law@redhat.com
+libc-971205               1997-09-10T21:16:20Z!law@redhat.com
+libc-971206               1997-09-10T21:16:20Z!law@redhat.com
+libc-971207               1997-09-10T21:16:20Z!law@redhat.com
+libc-971208               1997-09-10T21:16:20Z!law@redhat.com
+libc-971209               1997-09-10T21:16:20Z!law@redhat.com
+libc-971210               1997-09-10T21:16:20Z!law@redhat.com
+libc-971211               1997-09-10T21:16:20Z!law@redhat.com
+libc-971212               1997-09-10T21:16:20Z!law@redhat.com
+libc-971213               1997-09-10T21:16:20Z!law@redhat.com
+libc-971214               1997-09-10T21:16:20Z!law@redhat.com
+libc-971217               1997-09-10T21:16:20Z!law@redhat.com
+libc-971218               1997-09-10T21:16:20Z!law@redhat.com
+libc-971219               1997-09-10T21:16:20Z!law@redhat.com
+libc-971220               1997-09-10T21:16:20Z!law@redhat.com
+libc-971221               1997-09-10T21:16:20Z!law@redhat.com
+libc-971222               1997-09-10T21:16:20Z!law@redhat.com
+libc-971223               1997-09-10T21:16:20Z!law@redhat.com
+libc-971224               1997-09-10T21:16:20Z!law@redhat.com
+libc-971225               1997-09-10T21:16:20Z!law@redhat.com
+libc-971226               1997-09-10T21:16:20Z!law@redhat.com
+libc-971227               1997-09-10T21:16:20Z!law@redhat.com
+libc-971228               1997-09-10T21:16:20Z!law@redhat.com
+libc-971229               1997-09-10T21:16:20Z!law@redhat.com
+libc-971230               1997-09-10T21:16:20Z!law@redhat.com
+libc-971231               1997-09-10T21:16:20Z!law@redhat.com
+libc-980103               1997-09-10T21:16:20Z!law@redhat.com
+libc-980104               1997-09-10T21:16:20Z!law@redhat.com
+libc-980105               1997-09-10T21:16:20Z!law@redhat.com
+libc-980106               1997-09-10T21:16:20Z!law@redhat.com
+libc-980107               1997-09-10T21:16:20Z!law@redhat.com
+libc-980108               1997-09-10T21:16:20Z!law@redhat.com
+libc-980109               1997-09-10T21:16:20Z!law@redhat.com
+libc-980110               1997-09-10T21:16:20Z!law@redhat.com
+libc-980111               1997-09-10T21:16:20Z!law@redhat.com
+libc-980112               1997-09-10T21:16:20Z!law@redhat.com
+libc-980114               1997-09-10T21:16:20Z!law@redhat.com
+libc-980115               1997-09-10T21:16:20Z!law@redhat.com
+libc-980116               1997-09-10T21:16:20Z!law@redhat.com
+libc-980117               1997-09-10T21:16:20Z!law@redhat.com
+libc-980118               1997-09-10T21:16:20Z!law@redhat.com
+libc-980119               1997-09-10T21:16:20Z!law@redhat.com
+libc-980120               1997-09-10T21:16:20Z!law@redhat.com
+libc-980121               1997-09-10T21:16:20Z!law@redhat.com
+libc-980122               1997-09-10T21:16:20Z!law@redhat.com
+libc-980123               1997-09-10T21:16:20Z!law@redhat.com
+libc-980124               1997-09-10T21:16:20Z!law@redhat.com
+libc-980125               1997-09-10T21:16:20Z!law@redhat.com
+libc-980126               1997-09-10T21:16:20Z!law@redhat.com
+libc-980127               1997-09-10T21:16:20Z!law@redhat.com
+libc-980128               1997-09-10T21:16:20Z!law@redhat.com
+libc-980129               1998-01-28T18:01:29Z!ian@cygnus.com
+libc-980130               1998-01-28T18:01:29Z!ian@cygnus.com
+libc-980212               1998-02-03T18:27:31Z!kenner@gnu.org
+libc-980213               1998-02-03T18:27:31Z!kenner@gnu.org
+libc-980214               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980215               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980216               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980217               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980218               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980219               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980220               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980221               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980222               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980223               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980224               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980225               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980226               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980227               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980228               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980301               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980302               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980303               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980304               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980306               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980307               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980308               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980309               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980310               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980311               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980312               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980313               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980314               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980315               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980316               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980317               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980318               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980319               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980320               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980321               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980322               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980323               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980324               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980325               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980326               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980327               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980328               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980329               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980330               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980331               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980401               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980402               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980403               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980404               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980405               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980406               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980407               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980408               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980409               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980410               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980411               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980412               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980413               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980414               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980428               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980429               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980430               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980501               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980502               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980503               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980504               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980505               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980506               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980507               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980508               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980509               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980510               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980512               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980513               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980514               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980515               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980516               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980517               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980518               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980519               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980520               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980521               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980522               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980523               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980524               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980525               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980526               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980527               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980528               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980529               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980530               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980531               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980601               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980602               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980603               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980604               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980605               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980606               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980607               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980608               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980609               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980610               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980611               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980612               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980613               1998-02-13T12:16:46Z!kenner@gnu.org
+libc-980614               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980615               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980616               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980617               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980618               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980619               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980620               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980621               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980622               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980623               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980624               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980625               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980626               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980627               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980628               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980629               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980630               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980701               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980702               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980703               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980704               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980705               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980706               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980707               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980708               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980709               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980710               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980711               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980712               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980713               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980714               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980715               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980716               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980717               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980718               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980719               1998-06-13T19:51:10Z!kenner@gnu.org
+libc-980720               1998-07-19T22:11:47Z!rms@gnu.org
+libc_1_09                 1995-02-23T00:08:39Z!kenner@gnu.org
+make-3-72-9               1995-01-07T16:57:36Z!roland@gnu.org
+make-3-72-10              1995-01-07T16:57:36Z!roland@gnu.org
+make-3-72-11              1995-01-07T16:57:36Z!roland@gnu.org
+make-3-72-12              1995-01-07T16:57:36Z!roland@gnu.org
+make-3-72-13              1995-01-07T16:57:36Z!roland@gnu.org
+make-3-73                 1995-01-07T16:57:36Z!roland@gnu.org
+make-3-73-1               1995-01-07T16:57:36Z!roland@gnu.org
+make-3-73-2               1995-01-07T16:57:36Z!roland@gnu.org
+make-3-73-3               1995-05-10T15:03:48Z!roland@gnu.org
+make-3-74                 1995-05-10T15:03:48Z!roland@gnu.org
+make-3-74-1               1995-08-07T20:48:08Z!roland@gnu.org
+make-3-74-2               1995-08-07T20:48:08Z!roland@gnu.org
+make-3-74-3               1996-02-01T18:44:05Z!kwzh@gnu.org
+make-3-74-4               1996-03-20T01:08:11Z!roland@gnu.org
+make-3-74-5               1996-07-03T23:05:19Z!mrs@apple.com
+make-3-74-6               1996-07-03T23:05:19Z!mrs@apple.com
+make-3-74-7               1996-07-03T23:05:19Z!mrs@apple.com
+make-3-75                 1996-07-03T23:05:19Z!mrs@apple.com
+make-3-75-1               1997-07-22T21:35:43Z!rms@gnu.org
+make-3-75-91              1997-07-22T21:35:43Z!rms@gnu.org
+make-3-75-92              1997-08-14T02:16:15Z!eggert@twinsun.com
+make-3-75-93              1998-04-14T00:02:53Z!drepper@redhat.com
+make-3-76                 1997-09-05T21:01:56Z!psmith@BayNetworks.com
+make-3-76-1               1997-09-05T21:01:56Z!psmith@BayNetworks.com
+release-0-0               1996-07-16T04:47:46Z!kwzh@gnu.org
+release-0-1               1996-07-16T04:47:46Z!kwzh@gnu.org
+release-1-0               1997-04-11T20:40:28Z!ian@cygnus.com
+Release_5_25              1999-02-08T16:53:18Z!barry@zope.org
+root-libc-2_0_x-branch    1997-01-07T19:29:28Z!djm@gnu.org
diff --git a/admin/notes/unicode b/admin/notes/unicode
index 6db5bb7d05c..3901f60954f 100644
--- a/admin/notes/unicode
+++ b/admin/notes/unicode
@@ -1,12 +1,46 @@
                                             -*-mode: text; coding: utf-8;-*-
 
-Copyright (C) 2002-2013 Free Software Foundation, Inc.
+Copyright (C) 2002-2015 Free Software Foundation, Inc.
 See the end of the file for license conditions.
 
+Importing a new Unicode Standard version into Emacs
+-------------------------------------------------------------
+
+Emacs uses the following files from the Unicode Character Database
+(a.k.a. "UCD):
+
+  . UnicodeData.txt
+  . BidiMirroring.txt
+  . IVD_Sequences.txt
+
+First, these files need to be copied into admin/unidata/, and then
+Emacs should be rebuilt for them to take effect.  Rebuilding Emacs
+updates several derived files elsewhere in the Emacs source tree,
+mainly in lisp/international/.
+
+When Emacs is rebuilt for the first time after importing the new
+files, pay attention to any warning or error messages.  In particular,
+admin/unidata/unidata-gen.el will complain if UnicodeData.txt defines
+new bidirectional attributes of characters, because unidata-gen.el,
+bidi.c and dispextern.h need to be updated in that case; failure to do
+so will cause aborts in redisplay.
+
+Next, review the changes in UnicodeData.txt vs the previous version
+used by Emacs.  Any changes, be it introduction of new scripts or
+addition of codepoints to existing scripts, might need corresponding
+changes in the data used for filling the category-table, case-table,
+and char-width-table.  The additional scripts should cause automatic
+updates in charscript.el, but it is a good idea to look at the results
+and see if any changes in admin/unidata/blocks.awk are required.
+
+Any new scripts added by UnicodeData.txt will also need updates to
+script-representative-chars defined in fontset.el.  Other databases in
+fontset.el might also need to be updated as needed.
+
 Problems, fixmes and other unicode-related issues
 -------------------------------------------------------------
 
-Notes by fx to record various things of variable importance.  handa
+Notes by fx to record various things of variable importance.  Handa
 needs to check them -- don't take too seriously, especially with
 regard to completeness.
 
@@ -64,11 +98,11 @@ regard to completeness.
 
  * iso-2022 charsets get unified on i/o.
 
-        With the change on 2003-01-06, decoding routines put `charset'
-        property to decoded text, and iso-2022 encoder pay attention
+        With the change on 2003-01-06, decoding routines put the 'charset'
+        property onto decoded text, and iso-2022 encoder pay attention
         to it.  Thus, for instance, reading and writing by
         iso-2022-7bit preserve the original designation sequences.
-        The property name `preferred-charset' may be better?
+        The property name 'preferred-charset' may be better?
 
         We may have to utilize this property to decide a font.
 
@@ -134,8 +168,8 @@ nontrivial changes to the build process.
         leim/CXTERM-DIC/QJ.tit
         leim/CXTERM-DIC/SW.tit
         leim/CXTERM-DIC/TONEPY.tit
-        leim/MISC-DIC/pinyin.map
         leim/MISC-DIC/CTLau.html
+        leim/MISC-DIC/pinyin.map
         leim/MISC-DIC/ziranma.cin
 
  * cp850
@@ -154,19 +188,6 @@ nontrivial changes to the build process.
 
         leim/MISC-DIC/cangjie-table.cns
 
- * iso-latin-2
-
-     These files are processed by csplain, a program that requires
-     Latin-2 input.  In 2012 the csplain maintainers started
-     recommending UTF-8, but these files haven't been converted yet.
-
-        etc/refcards/cs-dired-ref.tex
-        etc/refcards/cs-refcard.tex
-        etc/refcards/cs-survival.tex
-        etc/refcards/sk-dired-ref.tex
-        etc/refcards/sk-refcard.tex
-        etc/refcards/sk-survival.tex
-
  * japanese-iso-8bit
 
      SKK-JISYO.L is a verbatim copy of a file taken from an external source.
@@ -181,13 +202,6 @@ nontrivial changes to the build process.
 
         admin/charsets/mapfiles/cns2ucsdkw.txt
 
- * no-conversion
-
-     This file purposely contains arbitrary bytes interspersed within text,
-     to test whether the Emacs distribution is corrupted.
-
-        lib-src/testfile
-
  * iso-2022-7bit
 
      This file switches between CJK charsets, which is not encoded in UTF-8.
@@ -201,11 +215,6 @@ nontrivial changes to the build process.
      operating in some other language environment.
 
         etc/tutorials/TUTORIAL.ja
-        leim/quail/cyril-jis.el
-        leim/quail/hanja-jis.el
-        leim/quail/japanese.el
-        leim/quail/py-punct.el
-        leim/quail/pypunct-b5.el
         lisp/international/ja-dic-cnv.el
         lisp/international/ja-dic-utl.el
         lisp/international/kinsoku.el
@@ -213,18 +222,47 @@ nontrivial changes to the build process.
         lisp/international/titdic-cnv.el
         lisp/language/japan-util.el
         lisp/language/japanese.el
-        lisp/term/x-win.el
+        lisp/leim/quail/cyril-jis.el
+        lisp/leim/quail/hanja-jis.el
+        lisp/leim/quail/japanese.el
+        lisp/leim/quail/py-punct.el
+        lisp/leim/quail/pypunct-b5.el
+
+     This file contains just Chinese characters, and has same problem.
+     Also, it contains characters that cannot be encoded in UTF-8.
+
+        lisp/international/titdic-cnv.el
 
  * utf-8-emacs
 
      These files contain characters that cannot be encoded in UTF-8.
 
-        leim/quail/tibetan.el
-        leim/quail/ethiopic.el
-        lisp/international/titdic-cnv.el
-        lisp/language/tibetan.el
-        lisp/language/tibet-util.el
+        lisp/language/ethio-util.el
+        lisp/language/ethiopic.el
         lisp/language/ind-util.el
+        lisp/language/tibet-util.el
+        lisp/language/tibetan.el
+        lisp/leim/quail/ethiopic.el
+        lisp/leim/quail/tibetan.el
+
+ * binary files
+
+     These files contain binary data, and are not text files.
+     Some of the entries in this list are patterns, and stand for any
+     files with the listed extension.
+
+        *.gz
+        *.icns
+        *.ico
+        *.pbm
+        *.pdf
+        *.png
+        *.sig
+        etc/e/eterm-color
+        etc/package-keyring.gpg
+        msdos/emacs.pif
+        nextstep/GNUstep/Emacs.base/Resources/emacs.tiff
+        nt/icons/hand.cur
 
 
 This file is part of GNU Emacs.
diff --git a/admin/notes/versioning b/admin/notes/versioning
new file mode 100644
index 00000000000..e422b22e432
--- /dev/null
+++ b/admin/notes/versioning
@@ -0,0 +1,26 @@
+GNU EMACS VERSIONING                                   -*- org -*-
+
+Ref: http://lists.gnu.org/archive/html/emacs-devel/2014-09/msg00872.html
+
+Emacs version numbers have the form
+
+  major.minor[.devel].build
+
+"build" increments each time Emacs is built in the same location
+(without cleaning) and isn't really part of the version.
+
+bugfix releases increase "minor" by 1.
+non-bugfix releases increase "major" by 1, and reset "minor" to 1.
+(The division between bugfix and non-bugfix has not always been clear
+historically.)
+
+Unreleased (development) versions have an extra "devel" component.
+This is a fairly meaningless number that may be unchanged for a long time.
+It is normally 50.
+When the release process starts, it changes to 90, 91, ...
+When the actual release is made, this component is removed.
+
+The development version for a new major release has "minor" = 0.
+The development version for a new minor release has "minor" = that of
+the previous release.
+
diff --git a/admin/notes/www b/admin/notes/www
index 0bb0850af0d..27aabe0766c 100644
--- a/admin/notes/www
+++ b/admin/notes/www
@@ -1,6 +1,6 @@
 -*- outline -*-
 
-Copyright (C) 2013 Free Software Foundation, Inc.
+Copyright (C) 2013-2015 Free Software Foundation, Inc.
 See the end of the file for license conditions.
 
 NOTES FOR EMACS WWW PAGES
diff --git a/admin/notes/years b/admin/notes/years
index e6b38c5aefd..c0db1854e30 100644
--- a/admin/notes/years
+++ b/admin/notes/years
@@ -2,6 +2,8 @@ HOW TO MAINTAIN COPYRIGHT YEARS FOR GNU EMACS
 
 Maintaining copyright years is now very simple: every time a new year
 rolls around, add that year to every FSF (and AIST) copyright notice.
+Do this by running the 'admin/update-copyright' script on a fresh repo
+checkout.  Inspect the results for plausibility, then commit them.
 
 There's no need to worry about whether an individual file has changed
 in a given year - it's sufficient that Emacs as a whole has changed.
@@ -28,10 +30,10 @@ but should keep the full list in a comment in the source.
  since Emacs 21 came out in 2001, all the subsequent years[1].  We don't
  need to check whether *that file* was changed in those years.
  It's sufficient that *Emacs* was changed in those years (and it was!).
-  
+
  For those files that have been added since then, we should add
  the year it was added to Emacs, and all subsequent years."
-  
+
  --RMS, 2005-07-13
 
 [1] Note that this includes 2001 - see