public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: "Joseph S. Myers" <jsm@polyomino.org.uk>
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
	Mark Mitchell <mark@codesourcery.com>,
	gcc@gcc.gnu.org
Subject: Re: PATCH: web/17495
Date: Fri, 17 Sep 2004 01:52:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.58.0409162117110.55757@dair.pair.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0409162307170.22891@digraph.polyomino.org.uk>

On Thu, 16 Sep 2004, Joseph S. Myers wrote:
> On Fri, 17 Sep 2004, Gerald Pfeifer wrote:
>
> > This sounds like an interesting suggestion.  It might be a bit tricky
> > due to different versions of GCC having different sets of manuals, and
> > I believe we currently do not have any scripting language (PHP,...) set
> > up on gcc.gnu.org, but perhaps a Perl/Shell script from cron.
> >
> > Joseph, you have been the one doing most work on the online manuals (and
> > a great job, by the way).  Do you have any ideas?
>
> The simplest
> suggestion would be a script or scripts to do some of the releasing steps
> that presently are manual, including updating webpages based on
> pre-existing markers in those pages of where to update.  The search page
> gets automatic monthly updates from a program run from htdigid's crontab
> (not gccadmin's), which might be something to look at to start with,

For reference, here it is, fresh from a "crontab -e".  It's the
last entry. See <URL:http://gcc.gnu.org/cvs.html#system> for the
CVS repos (except for the crontab below which isn't in CVS).

# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/crontab.3251 installed on Mon May 17 09:02:47 2004)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
17 8 1-31/2 * * /bin/sh /sourceware/htdig/gcc/bin/htupdate.sh
17 8 2-30/2 * * /bin/sh /sourceware/libre/infra/bin/htupdate-sourceware.sh
36 10 1 * * /bin/sh /sourceware/libre/infra/bin/munge-cvs-file /cvs/gcc wwwdocs/htdocs/search.html "Monthly update" /sourceware/libre/infra/bin/up-dates

brgds, H-P

      reply	other threads:[~2004-09-17  1:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <414866F1.1020300@codesourcery.com>
2004-09-16 23:28 ` Gerald Pfeifer
2004-09-17  0:02   ` Joseph S. Myers
2004-09-17  1:52     ` Hans-Peter Nilsson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.BSF.4.58.0409162117110.55757@dair.pair.com \
    --to=hp@bitrange.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=jsm@polyomino.org.uk \
    --cc=mark@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).