--- 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.