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
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
e4f1c3276a
Be more careful to avoid spurious output from the shell script that
...
unpacks the development version of the docs on SF.
2001-02-14 21:26:31 +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
d34cfcb4c7
Revise the message to be a little nicer.
...
Have the mail sent to the python-dev and Doc-SIG lists.
2000-10-29 13:21:45 +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