# HG changeset patch
# User David A. Holland
# Date 1653976597 14400
# Node ID 12171da8943f23df1ae48a6c27bb9e0d0951a9dd
# Parent  f9e4689b837d5e290e000024f31df7d16d859537
Don't refer to CVS.

diff -r f9e4689b837d -r 12171da8943f doc/devel/make.txt
--- a/doc/devel/make.txt	Tue May 31 01:45:26 2022 -0400
+++ b/doc/devel/make.txt	Tue May 31 01:56:37 2022 -0400
@@ -57,10 +57,10 @@
      run the most recent native agcl right out of the build tree.
      Use with due caution.
 
-   - The AG-generated code used in the build is kept in CVS, so
-     if all else fails you can revert to a clean version that way.
-     Be sure to revert matching .cpp and .h files, or the build 
-     will fail.
+   - The AG-generated code used in the build is kept in source
+     control, so if all else fails you can revert to a clean version
+     that way.  Be sure to revert matching .cpp and .h files, or the
+     build will fail.
 
 Note that $(TOP)/bin is neither created nor populated by default;
 if developing you should set it up yourself with a suitable agcl
diff -r f9e4689b837d -r 12171da8943f doc/devel/style.txt
--- a/doc/devel/style.txt	Tue May 31 01:45:26 2022 -0400
+++ b/doc/devel/style.txt	Tue May 31 01:56:37 2022 -0400
@@ -100,7 +100,7 @@
 ifdefs:
 
    - Use #ifdef AG_ON_UNIX and #ifdef AG_ON_WINDOWS for
-     platform-specific code. Don't use compiler ifdefs for this;
+     platform-specific code. Don't use per-compiler ifdefs for this;
      in the long run compilers are more portable than you think.
 
    - Don't use #ifndef AG_ON_UNIX or #ifndef AG_ON_WINDOWS, unless
diff -r f9e4689b837d -r 12171da8943f doc/devel/versions.txt
--- a/doc/devel/versions.txt	Tue May 31 01:45:26 2022 -0400
+++ b/doc/devel/versions.txt	Tue May 31 01:56:37 2022 -0400
@@ -18,15 +18,14 @@
 and increments the build number. Needless to say, you don't commit to
 the stable branch lightly.
 
- - A development version built directly from a CVS or Mercurial
+ - A development version built directly from a Mercurial or Git
 working directory will be numbered 2.40-current, because it's difficult or
 impossible to ascertain the proper date. Assuming the proper date is
-even well defined.
+even well defined; after all, most such builds happen while coding and
+include uncommitted changes.
 
- - A stable version built directly from a CVS or Mercurial working
+ - A stable version built directly from a Mercurial or Git working
 directory will be numbered 2.40.01-current.
 
- - If we set up anoncvs, which if properly managed is equivalent to
-issuing a devel snapshot every night, it should be possible to inject
-the date.
-
+ - Note that while injecting the last committed change hash in these
+circumstances is possible, it isn't worthwhile.