- change computation of VERSION to use tools/getversioninfo; this is
  more reliable than using the $Revision$ expansion
- $RELEASE is no longer needed; we can just use $VERSION now

but check it in on the right branch this time

to be archived.  Most of these are pretty bland.  ;-)

when the changes are just too small.

release being discussed.

update announcements do not get bounces from trying to send mail to my
laptop, which has an identity crisis due to constant relocation.

Add a -F option similar to "cvs commit -F <file>".
Add a -t option to allow specifying the prefix to the directory into which
the docs should be unpacked (useful when I start trying out new styles for
the presentation).

branch is the head (development) branch or a maintenance brach, and use
the appropriate target directory for each.

this version avoids having to build a separate authenticated connection
to push the update-docs.sh script to SF.

site.  These now seem (slightly) more reliable, and easier to work with
since update-docs.sh no longer needs to be installed ahead of time on
my account at SF.

notification message.

just sitting around in my working directory.

Python documentation.