[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] trunk r116043: Minor correction to admin/notes/bzr: *fourt
From: |
Eric S. Raymond |
Subject: |
[Emacs-diffs] trunk r116043: Minor correction to admin/notes/bzr: *fourth* VCS, not third. |
Date: |
Thu, 16 Jan 2014 15:05:25 +0000 |
User-agent: |
Bazaar (2.6b2) |
------------------------------------------------------------
revno: 116043
revision-id: address@hidden
parent: address@hidden
committer: Eric S. Raymond <address@hidden>
branch nick: trunk
timestamp: Thu 2014-01-16 10:05:18 -0500
message:
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."
modified:
admin/notes/commits cvslogs-20091113204419-o5vbwnq5f7feedwu-8580
=== modified file 'admin/notes/commits'
--- a/admin/notes/commits 2014-01-16 05:50:26 +0000
+++ b/admin/notes/commits 2014-01-16 15:05:18 +0000
@@ -45,10 +45,10 @@
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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] trunk r116043: Minor correction to admin/notes/bzr: *fourth* VCS, not third.,
Eric S. Raymond <=