public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: jit@gcc.gnu.org, gcc-patches@gcc.gnu.org
Cc: Gerald Pfeifer <gerald@pfeifer.com>, Jeff Law <law@redhat.com>,
	David Malcolm <dmalcolm@redhat.com>
Subject: [PATCH] maintainer-scripts: Fix 404s in "Show Source" in jit docs
Date: Thu, 01 Jan 2015 00:00:00 -0000	[thread overview]
Message-ID: <1423194586-39286-1-git-send-email-dmalcolm@redhat.com> (raw)
In-Reply-To: <1423088766.29180.129.camel@surprise>

Tested locally with a suitably hacked up script to work on this
machine; with this patch the "Show Sources" links work within the
files installed to /www/gcc/htdocs.

OK for trunk?

maintainer-scripts/ChangeLog:
	* update_web_docs_svn: When copying up files for the built jit
	documentation, also copy up .txt files.
---
 maintainer-scripts/update_web_docs_svn | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/maintainer-scripts/update_web_docs_svn b/maintainer-scripts/update_web_docs_svn
index 2544211..7832eed 100755
--- a/maintainer-scripts/update_web_docs_svn
+++ b/maintainer-scripts/update_web_docs_svn
@@ -233,10 +233,12 @@ done
 
 # Again, the jit is a special case, with nested subdirectories
 # below "jit", and with some non-HTML files (.png images from us,
-# plus .css and .js supplied by sphinx).
+# plus .css and .js supplied by sphinx, and source files, renamed
+# from .rst to .txt).
 find jit \
     -name "*.html" -o -name "*.png" \
-    -o -name "*.css" -o -name "*.js" |
+    -o -name "*.css" -o -name "*.js" \
+    -o -name "*.txt" |
   while read file ; do
     # Note that $file here will contain path fragments beginning
     # with "jit/", e.g. "jit/cp/topics/functions.html"
-- 
1.8.5.3

  reply	other threads:[~2015-02-06  3:40 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 docs (PR jit/64257) David Malcolm
2015-01-01  0:00 ` Gerald Pfeifer
2015-01-01  0:00   ` Mike Stump
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
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 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

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=1423194586-39286-1-git-send-email-dmalcolm@redhat.com \
    --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).