public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Jason Merrill <jason@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. f2df0e85a75108dc2878852f727fdabd6a98e03f
Date: Tue,  5 Oct 2021 19:55:12 +0000 (GMT)	[thread overview]
Message-ID: <20211005195512.A70F6385802D@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  f2df0e85a75108dc2878852f727fdabd6a98e03f (commit)
      from  b99e91019bbb63d17eea6e5d75e8b9bc2a9b81cc (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 f2df0e85a75108dc2878852f727fdabd6a98e03f
Author: Jason Merrill <jason@redhat.com>
Date:   Tue Oct 5 15:55:00 2021 -0400

    contribute: add some helpful commands

diff --git a/htdocs/contribute.html b/htdocs/contribute.html
index c0cce359..423ce9de 100644
--- a/htdocs/contribute.html
+++ b/htdocs/contribute.html
@@ -183,8 +183,12 @@ testcases cannot be added.
 A ChangeLog entry as plaintext; see the <a href="codingconventions.html#ChangeLogs">GCC
 coding conventions</a> and <a
 href="http://www.gnu.org/prep/standards_toc.html">GNU Coding
-Standards</a> for further information.</dd>
+Standards</a> for further information.
 
+<br/>The <code>git gcc-commit-mklog</code> command from
+<code>gcc-git-customization.sh</code> (see <a href="gitwrite.html">here</a>)
+automates a lot of ChangeLog generation.
+</dd>
 <dt>Bootstrapping and testing</dt>
 <dd>
 State the host and target combinations you used to do <a
@@ -369,6 +373,14 @@ original thread indicating that a new version has been submitted.</p>
   <li><code>[PATCH v2] wwwdocs: E-mail subject lines for contributions</code></li>
 </ul>
 
+<h4>git format-patch/send-email</h4>
+
+The <code>git format-patch</code> tool generates an email in the desired
+format, with the commit subject line as the email subject line
+with <code>[PATCH]</code> prepended.  You can send the resulting file as an
+email by itself (perhaps with <code>git send-email</code>) or as an attachment
+to another email.
+
 <h3>Pinging patches, Getting patches applied</h3>
 
 <p>If you do not receive a response to a patch that you have submitted

-----------------------------------------------------------------------

Summary of changes:
 htdocs/contribute.html | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2021-10-05 19:55 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=20211005195512.A70F6385802D@sourceware.org \
    --to=jason@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: 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).