From c48003a53cbeee75dd34f5c3932a60ee97defb28 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Mon, 21 Sep 2009 08:56:17 +0200 Subject: maint: automate the web-doc updating procedure * gnu-web-doc-update: New script, destined for gnulib. * README-release: Refer to the new script. --- README-release | 13 ++----------- 1 file changed, 2 insertions(+), 11 deletions(-) (limited to 'README-release') diff --git a/README-release b/README-release index 8dcab9798..d20a9118c 100644 --- a/README-release +++ b/README-release @@ -81,17 +81,8 @@ Once all the builds and tests have passed, Then go here to approve it: https://savannah.gnu.org/news/approve.php?group=coreutils -* For non-alpha releases, update the on-line manual at +* After each non-alpha release, update the on-line manual accessible via http://www.gnu.org/software/coreutils/manual/ - Run `make web-manual', then copy the contents of doc/manual - into a CVS checkout of the coreutils manual repository. - Also edit coreutils.html (FIXME? why?) before doing a CVS commit. - - CVS_RSH=ssh \ - cvs -d:ext:$USER@cvs.savannah.gnu.org:/web/coreutils co coreutils - - Be sure to "cvs add -ko" any files that "cvs status" marks with "?". - That is necessary whenever a new texinfo node is added. Each becomes - a new file in html_node that must then be "cvs add"ed. + by running the gnu-web-doc-update script. -- cgit v1.2.3-70-g09d2