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] maintainer-scripts: Fix 404s in "Show Source" in jit docs
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.11.1502061523130.2504@tuna.site> (raw)
In-Reply-To: <1423194586-39286-1-git-send-email-dmalcolm@redhat.com>
On Thursday 2015-02-05 22:49, David Malcolm wrote:
> 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.
Sure thing. You should just consider yourself the maintainer of
this aspect and simply go ahead with changes like this.
Gerald
next prev parent reply other threads:[~2015-02-06 14:24 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
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 [this message]
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 ` 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=alpine.LSU.2.11.1502061523130.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).