SRC support in Emacs.

diff --git a/FAQ.asc b/FAQ.asc
index 707e0a0c58af96596c8bf3416e76712859a4df61..56b91b594f33491eb9ab08b1ee925498b2cc691d 100644 (file)
--- a/FAQ.asc
+++ b/FAQ.asc
@@ -1,5 +1,5 @@
 = SRC FAQ =
-version 1.0
+version 1.1
 
 [[why]]
 == Why SRC instead of $VCS? ==
@@ -88,6 +88,10 @@ also wrote.  SRC has a couple of advantages over VC-RCS - running
 lockless, better scriptability, and ditching RCS's awful revision
 numbering are the main ones.
 
+SRC is now a fully-supported VC-mode system in the Emacs development
+tree, so you can run SRC through Emacs and get the lockless operation
+and Subversion-style revision numbers.
+
 [[beginners-vcs]]
 == Is SRC a good system on which to learn about version control? ==
 

diff --git a/src.asc b/src.asc
index 1fc57c88975a0143079c312092e5bd5cf8a3c06b..443f56c2499bdf43c9a992f7d3209ede05432144 100644 (file)
--- a/src.asc
+++ b/src.asc
@@ -28,6 +28,9 @@ to look familiar if you have ever used Subversion, Mercurial, or Git.
 SRC interprets the EDITOR variable in the usual way, using it to spawn
 an editor instance when you perform a commit or amend.
 
+SRC is fully supported in Emacs VC mode, though at time of writing
+only in the development tree.
+
 == COMMAND SUMMARY ==
 
 A 'revision' is a 1-origin integer, or a tag name designating an
@@ -168,8 +171,9 @@ output of "git status *" will list them with status "I".
 
 == BACKWARD COMPATIBILITY ==
 
-SRC history files are RCS master files. SRC maintains no state other
-than these files.
+SRC history files are RCS master files. SRC maintains no permanent
+state other than these files.  It keeps some transient state as
+stamp files to speed up 'src sratus'.
 
 In order to maintain complete backwards compatibility, one compromise
 was made: any commit comment containing a string exactly matching an