public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. dbc2cba91f4840426b875685c0b9c2807a5870da Date: Mon, 20 Jul 2020 08:32:47 +0000 (GMT) [thread overview] Message-ID: <20200720083247.17F1E385DC0F@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via dbc2cba91f4840426b875685c0b9c2807a5870da (commit) from cd0f4f8c0d9c6da95137a9b76bd64f7054a10d61 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit dbc2cba91f4840426b875685c0b9c2807a5870da Author: Hu Jiangping <hujiangping@cn.fujitsu.com> Date: Thu Jul 16 16:21:03 2020 +0800 projects/tree-ssa: add a big banner to tree-browser.html Add a big banner to say that the page is no longer up-to-date. diff --git a/htdocs/projects/tree-ssa/tree-browser.html b/htdocs/projects/tree-ssa/tree-browser.html index ce95a103..fe292b49 100644 --- a/htdocs/projects/tree-ssa/tree-browser.html +++ b/htdocs/projects/tree-ssa/tree-browser.html @@ -8,6 +8,11 @@ </head> <body> + + <!-- banner --> + <p class="bold"><br /><br />Tree Browser has been removed from gcc, +and this page is no longer up-to-date.<br /><br /><br /></p> + <hr /> <h1>Tree Browser</h1> <p>Until recently the only way to debug trees from gdb was to call ----------------------------------------------------------------------- Summary of changes: htdocs/projects/tree-ssa/tree-browser.html | 5 +++++ 1 file changed, 5 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-07-20 8:32 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200720083247.17F1E385DC0F@sourceware.org \ --to=rsandifo@sourceware.org \ --cc=gcc-cvs-wwwdocs@gcc.gnu.org \ /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: linkBe 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).