summaryrefslogtreecommitdiff
path: root/admin
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2014-01-16 10:05:18 -0500
committerEric S. Raymond <esr@thyrsus.com>2014-01-16 10:05:18 -0500
commit4d6df42066b762ba12191ba6dec82cda96ac21d3 (patch)
tree441e1e0d138ebabe1b5f52293fc141f339f5e2af /admin
parent2dbf4ffdda88a57842a07b8a4658858df34b47bc (diff)
downloademacs-4d6df42066b762ba12191ba6dec82cda96ac21d3.tar.gz
Minor correction to admin/notes/bzr: *fourth* VCS, not third.
RCS -> CVS -> Bzr -> Git. And (as Stefan Monnier reports) "GNU Arch was semi-officially used for a while between CVS and Bzr, tho not for the main branch."
Diffstat (limited to 'admin')
-rw-r--r--admin/notes/commits4
1 files changed, 2 insertions, 2 deletions
diff --git a/admin/notes/commits b/admin/notes/commits
index 6e2aabe5abc..f33c6905d4c 100644
--- a/admin/notes/commits
+++ b/admin/notes/commits
@@ -45,10 +45,10 @@ Date: Tue, 31 Mar 2009 12:21:20 +0900
for modern source-control systems with a global log, it's better to
have something like "Regenerate configure".
-(4) (Added in 2014) In commit comments, and ChangLog files, it is best
+(4) (Added in 2014) In commit comments, and ChangeLog files, it is best
to use ways of identifying revisions that are not dependent on a
particular version control system. (At time of writing Emacs is
- about to move to its third VCS and another move in the future is
+ about to move to its fourth VCS and another move in the future is
not impossible.) An excellent way to identify commits is by
quoting their summary line. Another is with an action stamp - an
RFC3339 date followed by ! followed by the committer's email - for