public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 4a56e1431bd0e2e3d435168216d7beec462b004a Date: Mon, 19 Feb 2024 10:36:08 +0000 (GMT) [thread overview] Message-ID: <20240219103608.33FDC386187E@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 4a56e1431bd0e2e3d435168216d7beec462b004a (commit) from a8228fa92ff2ced72d02801e374f7d4c5ed40683 (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 4a56e1431bd0e2e3d435168216d7beec462b004a Author: Florian Weimer <fweimer@redhat.com> Date: Mon Feb 19 11:35:47 2024 +0100 CSS: Color markup for <ins>/<del> In addition to underlines and strikethroughs. This makes it easier to spot the differences in example code changes. diff --git a/htdocs/gcc.css b/htdocs/gcc.css index 77d01ee0..e32c4b93 100644 --- a/htdocs/gcc.css +++ b/htdocs/gcc.css @@ -98,6 +98,10 @@ div.copyright p:nth-child(3) { margin-bottom: 0; } .blue { color:blue; } .blackbg { color:white; background-color: #000000; } +/* Inline markup for differences. */ +ins { background-color: lightgreen } +del { background-color: pink } + /* Quote an e-mail. The first <div> has the sender, the second the quote. */ blockquote.mail div:nth-child(2) { border-left: solid blue; padding-left: 4pt; } ----------------------------------------------------------------------- Summary of changes: htdocs/gcc.css | 4 ++++ 1 file changed, 4 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2024-02-19 10:36 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=20240219103608.33FDC386187E@sourceware.org \ --to=fw@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).