From: David Malcolm <dmalcolm@redhat.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: jit@gcc.gnu.org, gcc-patches@gcc.gnu.org, Jeff Law <law@redhat.com>
Subject: Re: [PATCH] More fixes for update_web_docs_svn for jit docs (PR jit/64257)
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <1423099046.31674.4.camel@surprise> (raw)
In-Reply-To: <1423088766.29180.129.camel@surprise>
On Wed, 2015-02-04 at 17:26 -0500, David Malcolm wrote:
> On Wed, 2015-02-04 at 22:21 +0100, Gerald Pfeifer wrote:
> > On Wednesday 2015-02-04 14:10, David Malcolm wrote:
> > > Gerald: Please can you do the "svn up" on the relevant machine again,
> > > so that it gets the updated "update_web_docs_svn"?
> >
> > That was my plan, yes. :-) I just did that and manually ran
> > the script, and it seems to work.
>
> Thank you!
>
> The jit docs are now visible on the GCC website at:
> https://gcc.gnu.org/onlinedocs/jit/
and fwiw:
https://gcc.gnu.org/ml/gccadmin/2015-q1/msg00080.html
shows that the cronjob then successfully rebuilt them again from svn.
> (sadly the "Show Source" link on each page is a 404; iirc the "pyramid"
> theme didn't show these links so I didn't bother copying up the files;
> I'll look at fixing that).
>
> > Still, do you think you can add a bit of error handling such
> > that an issue like the one we had (cf.
> > https://gcc.gnu.org/ml/gccadmin/2015-q1/msg00077.html ) does
> > not kill the entire script? A bit of resilience would be good.
>
> Something like the attached? (completely untested, sorry)
>
next prev parent reply other threads:[~2015-02-05 1:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 [PATCH] update_web_docs_svn: support the JIT " David Malcolm
2015-01-01 0:00 ` Gerald Pfeifer
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Jeff Law
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` [PING, www] " David Malcolm
2015-01-01 0:00 ` Gerald Pfeifer
2015-01-01 0:00 ` [PATCH] More fixes for update_web_docs_svn for jit " David Malcolm
2015-01-01 0:00 ` Andrew Pinski
2015-01-01 0:00 ` Gerald Pfeifer
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Gerald Pfeifer
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` David Malcolm [this message]
2015-01-01 0:00 ` [PATCH] maintainer-scripts: Fix 404s in "Show Source" in jit docs David Malcolm
2015-01-01 0:00 ` Gerald Pfeifer
2019-01-01 0:00 ` [PATCH] More fixes for update_web_docs_svn for jit docs (PR jit/64257) Gerald Pfeifer
2015-01-01 0:00 ` [PATCH] update_web_docs_svn: support the JIT " Mike Stump
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=1423099046.31674.4.camel@surprise \
--to=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jit@gcc.gnu.org \
--cc=law@redhat.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).