public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 6f0743aeca7a1a18089229a0defd23cf44d3e453 Date: Tue, 1 Nov 2022 09:45:08 +0000 (GMT) [thread overview] Message-ID: <20221101094508.4D8F83858D35@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 6f0743aeca7a1a18089229a0defd23cf44d3e453 (commit) from 0550eba8036643fbb9528298f51b07caf608c847 (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 6f0743aeca7a1a18089229a0defd23cf44d3e453 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Tue Nov 1 10:44:02 2022 +0100 projects/tree-ssa: Adjust mark up Remove extraneous whitespace around heading and adjust level. diff --git a/htdocs/projects/tree-ssa/tree-browser.html b/htdocs/projects/tree-ssa/tree-browser.html index 23f46e92..a6ffc46b 100644 --- a/htdocs/projects/tree-ssa/tree-browser.html +++ b/htdocs/projects/tree-ssa/tree-browser.html @@ -298,7 +298,8 @@ else TB> </pre> - <h1> Extensions </h1> + +<h2>Extensions</h2> <p>Some extensions could be added in the near future, such as including commands that allows you to modify tree structure, apply optimizations ----------------------------------------------------------------------- Summary of changes: htdocs/projects/tree-ssa/tree-browser.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-11-01 9:45 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=20221101094508.4D8F83858D35@sourceware.org \ --to=gerald@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).