From: Gerald Pfeifer <gerald@pfeifer.com>
To: David Malcolm <dmalcolm@redhat.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: <alpine.LSU.2.11.1502041946290.2504@tuna.site> (raw)
In-Reply-To: <1423074736-47636-1-git-send-email-dmalcolm@redhat.com>
On Wednesday 2015-02-04 13:32, David Malcolm wrote:
> OK for trunk?
>
> gcc/jit/ChangeLog:
> PR jit/64257
> * docs/conf.py (html_theme): Change from 'pyramid'
> to 'sphinxdoc'.
>
> maintainer-scripts/ChangeLog:
> PR jit/64257
> * update_web_docs_svn: Update build of jit docs to use EPEL6
> variant install of sphinx 1.0.8, rather than 0.6.6.
Yes.
> +# python-sphinx10 package. The latter installs its executable as:
Here I'd omit the colon, but that is more of a stylistic question
I guess.
Gerald
next prev parent reply other threads:[~2015-02-04 18:47 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 ` Gerald Pfeifer [this message]
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 ` [PATCH] maintainer-scripts: Fix 404s in "Show Source" in jit docs David Malcolm
2015-01-01 0:00 ` Gerald Pfeifer
2015-01-01 0:00 ` [PATCH] More fixes for update_web_docs_svn for jit docs (PR jit/64257) David Malcolm
2019-01-01 0:00 ` Gerald Pfeifer
2015-01-01 0:00 ` Andrew Pinski
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=alpine.LSU.2.11.1502041946290.2504@tuna.site \
--to=gerald@pfeifer.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--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).