From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hamza.pair.com (hamza.pair.com [209.68.5.143]) by sourceware.org (Postfix) with ESMTPS id 802C93857B99 for ; Wed, 19 Oct 2022 14:13:41 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 802C93857B99 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=pfeifer.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=pfeifer.com Received: from hamza.pair.com (localhost [127.0.0.1]) by hamza.pair.com (Postfix) with ESMTP id 3218C33E1B for ; Wed, 19 Oct 2022 10:13:41 -0400 (EDT) Received: from naga.localdomain (194-166-101-219.adsl.highway.telekom.at [194.166.101.219]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by hamza.pair.com (Postfix) with ESMTPSA id C263933E8D for ; Wed, 19 Oct 2022 10:13:40 -0400 (EDT) Date: Wed, 19 Oct 2022 16:13:38 +0200 (CEST) From: Gerald Pfeifer To: gcc-patches@gcc.gnu.org Subject: [committed] wwwdocs: codingconventions: Fix two typos MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Scanned-By: mailmunge 3.09 on 209.68.5.143 Message-Id: <20221019141341.3218C33E1B@hamza.pair.com> X-Spam-Status: No, score=-10.6 required=5.0 tests=BAYES_00,GIT_PATCH_0,KAM_DMARC_STATUS,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: I looked for some typos to test whether updating individual pages now works smoothly again after my mass update a few days ago ran into a problem on the server side and left the system in "twilight zone". Pushed. Gerald --- htdocs/codingconventions.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html index c793058f..9d0a3f14 100644 --- a/htdocs/codingconventions.html +++ b/htdocs/codingconventions.html @@ -142,7 +142,7 @@ a large batch of changes.

supported formats: a/b/c/ChangeLog, a/b/c/ChangeLog:, a/b/c/ (where ChangeLog file lives in the folder), \ta/b/c/ and a/b/c
  • pr_entry - bug report reference
    example: \tPR component/12345
    • -
  • changelog_file - a modified file mentined in a ChangeLog: +
  • changelog_file - a modified file mentioned in a ChangeLog: supported formats: \t* a/b/c/file.c:, \t* a/b/c/file.c (function):, \t* a/b/c/file1.c, a/b/c/file2.c:
  • changelog_file_comment - line that follows a changelog_file with description of changes in the file; must start with \t
    • @@ -154,7 +154,7 @@ a large batch of changes.

    Format rules

      -
    • git_description - optional; ends right before one of the other compoments is found
      • +
    • git_description - optional; ends right before one of the other components is found
    • committer_timestamp - optional; when found before a changelog_file, then it is added to each changelog entry
    • additional_author - optional
      • -- 2.38.0