public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 15417e5e260c1299a07ea32911b401f321e29f3a Date: Mon, 15 Jun 2020 09:35:17 +0000 (GMT) [thread overview] Message-ID: <20200615093517.14EA73851C20@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 15417e5e260c1299a07ea32911b401f321e29f3a (commit) from 94e51dd51b4cc699592cc40bf78687920a9a2f4a (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 15417e5e260c1299a07ea32911b401f321e29f3a Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Jun 15 10:35:10 2020 +0100 Make plain text requirement more descriptive diff --git a/htdocs/lists.html b/htdocs/lists.html index df45edd7..bf6a0dc4 100644 --- a/htdocs/lists.html +++ b/htdocs/lists.html @@ -166,7 +166,8 @@ this size, you should compress any attachments before sending it to the list. <p>When posting messages, please select an appropriate list for the message and try to avoid cross posting to several lists.</p> -<p>Please send plain text (as opposed to HTML, RTF,...).</p> +<p>Please send plain text +(as opposed to HTML, RTF, or other types with fancy formatting).</p> <p id="confidential">Do not include or reference confidentiality notices, like:</p> ----------------------------------------------------------------------- Summary of changes: htdocs/lists.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-06-15 9:35 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=20200615093517.14EA73851C20@sourceware.org \ --to=redi@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).