1681b62251
add another way to specify an alternate name for the documentation set,
...
so that this is harder to forget to do for development of new styles
2004-11-13 17:45:39 +00:00
eac00edd20
fix accidental commit
2004-11-02 19:20:43 +00:00
303e30ef9f
clarify discussion of iteration in the section on the "for" statement
...
(SF bug #829073 )
2004-11-02 19:18:20 +00:00
96b935e643
fix handling when a proper getopt(1) is available; the "--"
...
end-of-options marker wasn't recognized
2004-06-29 14:39:06 +00:00
964c798a94
Use getopt where possible, so this supports option letters that get
...
jammed together on thos platforms.
2004-06-17 22:04:17 +00:00
9e1ac2496f
- add link to the downloadable package in the generated email
...
- misc. changes
2004-06-17 18:36:54 +00:00
69db2b967a
- 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
2003-09-28 22:14:29 +00:00
e13602ee49
Mark the notice about the new development version of the docs as not needing
...
to be archived. Most of these are pretty bland. ;-)
2002-04-04 18:06:06 +00:00
f54519d9e4
Update to push the docs to python.org instead of python.sf.net.
2002-04-01 20:15:05 +00:00
a281665972
No need to run make twice here.
2001-10-25 15:13:30 +00:00
e54acfd8b2
Add option to push the development docs to SF without announcing, for
...
when the changes are just too small.
2001-08-08 05:41:01 +00:00
602cf584be
Generate a more meaningful message regarding the type of the documentation
...
release being discussed.
2001-07-12 21:50:10 +00:00
de6dc1e11c
Change the way notification mails are sent so people who respond to the
...
update announcements do not get bounces from trying to send mail to my
laptop, which has an identity crisis due to constant relocation.
2001-07-06 23:45:16 +00:00
66a0a0a9b6
Make the option processing more robust.
...
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).
2001-06-12 13:31:37 +00:00
283b352d48
Update the directory names to match changes at SourceForge.
2001-05-09 16:33:34 +00:00
34b48e844e
Update publish-to-SourceForge scripts to automatically determine if the
...
branch is the head (development) branch or a maintenance brach, and use
the appropriate target directory for each.
2001-04-22 06:20:31 +00:00
e1f3ed6b58
Update the helper scripts that push development docs to SourceForge;
...
this version avoids having to build a separate authenticated connection
to push the update-docs.sh script to SF.
2001-04-13 05:13:55 +00:00
0c8f6643c6
Remove debugging "set -x".
2001-03-03 19:57:26 +00:00
3f4e717c31
Revise the scripts I use to update the documentation on the SourceForge
...
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.
2001-03-02 21:05:58 +00:00
827bb9fb3c
Adjust to allow an explanation of the changes to be included in the
...
notification message.
2000-11-30 07:38:59 +00:00
7ceab739d0
Make this actually work now that the tool is checked in here instead of
...
just sitting around in my working directory.
2000-10-24 19:59:55 +00:00
692565c9e9
Helper scripts used in published the "development" snapshots of the
...
Python documentation.
2000-10-19 05:54:51 +00:00
Fred Drake