public inbox for
help / color / mirror / Atom feed
From: Jason Merrill <>
Subject: gcc-wwwdocs branch master updated. 74b4ad47414593cfbf3325c41c587c5447b0a75e
Date: Wed,  7 Sep 2022 13:53:16 +0000 (GMT)	[thread overview]
Message-ID: <> (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  74b4ad47414593cfbf3325c41c587c5447b0a75e (commit)
      from  7ecde930138f8cef11b492174beb146a040d99a3 (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 74b4ad47414593cfbf3325c41c587c5447b0a75e
Author: Jason Merrill <>
Date:   Tue Aug 23 13:27:15 2022 -0400

    contribute: link to kernel doc about patch email

diff --git a/htdocs/contribute.html b/htdocs/contribute.html
index c985b87d..6e72e96f 100644
--- a/htdocs/contribute.html
+++ b/htdocs/contribute.html
@@ -237,6 +237,11 @@ changing.)  For further information on our source repository, see
 the <a href="git.html">Anonymous read-only Git access</a> and <a
 href="gitwrite.html">Read-write Git access</a> pages.</p>
+<p>Many mail clients break patches pasted into the message body, primarily by
+wrapping long lines.  See
+<a href="">
+the Linux kernel documentation</a> for ways to work around this.</p>
 <p>(Everything listed here still applies if you can check in the patch
 without further approval under the <a
 href="gitwrite.html#policies">GCC write access policies</a>, except


Summary of changes:
 htdocs/contribute.html | 5 +++++
 1 file changed, 5 insertions(+)


                 reply	other threads:[~2022-09-07 13:53 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).