From patchwork Sun Nov 26 10:14:02 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Gerald Pfeifer X-Patchwork-Id: 841326 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=gcc.gnu.org (client-ip=209.132.180.131; helo=sourceware.org; envelope-from=gcc-patches-return-467907-incoming=patchwork.ozlabs.org@gcc.gnu.org; receiver=) Authentication-Results: ozlabs.org; dkim=pass (1024-bit key; unprotected) header.d=gcc.gnu.org header.i=@gcc.gnu.org header.b="CvYuW7iL"; dkim-atps=neutral Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 3yl5Pl4q10z9s3w for ; Sun, 26 Nov 2017 21:14:16 +1100 (AEDT) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gcc.gnu.org; h=list-id :list-unsubscribe:list-archive:list-post:list-help:sender:date :from:to:subject:message-id:mime-version:content-type; q=dns; s= default; b=a5V3AXRszzC4dwDRRiU3qidqKP7Riwuz5sMAPpkDJ2iBHIF5hVM6d q1YEWkB4Kn4gx8TgEd4Q8OJXBMuNYVxSBQxaYudE8TX5IrKq+VLmcPo7iH5+A8dM gw1YzIysvAXav/CTeLknPog1RTmegRHDyJ4YvE07UoT21AgogOpoAs= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gcc.gnu.org; h=list-id :list-unsubscribe:list-archive:list-post:list-help:sender:date :from:to:subject:message-id:mime-version:content-type; s= default; bh=r7Aig7pMp72ar44Ybckv8vOzxFU=; b=CvYuW7iLJggahlzRPV3h pMR7LXCguWVPvKwi6L0V7opawGxusna/hFpuxJypXFyBj5lBUYsgK5T3tentlnCi K0Y0c6/TLK89p725y1jcq+UWgghKLXbu4+hfUpnXN2j1MstW2q4utxKgtCuN3PlY PY7opbyxSowb0LECFa/BDaY= Received: (qmail 116538 invoked by alias); 26 Nov 2017 10:14:08 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Delivered-To: mailing list gcc-patches@gcc.gnu.org Received: (qmail 116523 invoked by uid 89); 26 Nov 2017 10:14:07 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-11.7 required=5.0 tests=BAYES_00, GIT_PATCH_2, GIT_PATCH_3, KB_WAM_FROM_NAME_SINGLEWORD, RCVD_IN_DNSWL_NONE, SPF_PASS autolearn=ham version=3.3.2 spammy=Enter, streamline, planned, 14, 8 X-HELO: ainaz.pair.com Received: from ainaz.pair.com (HELO ainaz.pair.com) (209.68.2.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 26 Nov 2017 10:14:06 +0000 Received: from ainaz.pair.com (localhost [127.0.0.1]) by ainaz.pair.com (Postfix) with ESMTP id C18773F496 for ; Sun, 26 Nov 2017 05:14:04 -0500 (EST) Received: from anthias (vie-188-118-240-174.dsl.sil.at [188.118.240.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ainaz.pair.com (Postfix) with ESMTPSA id 4DE793F444 for ; Sun, 26 Nov 2017 05:14:04 -0500 (EST) Date: Sun, 26 Nov 2017 11:14:02 +0100 (CET) From: Gerald Pfeifer To: gcc-patches@gcc.gnu.org Subject: [wwwdocs] bugs/management.html: add a link, streamline a bit Message-ID: MIME-Version: 1.0 X-IsSubscribed: yes Looking for something Jonathan pointed out, I noticed (again) that our language is a bit verbose around our bug reporting / management instructions. Applied Gerald Add a link to our bug reporting instructions. Trim some language. Index: management.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/management.html,v retrieving revision 1.32 diff -u -r1.32 management.html --- management.html 3 Mar 2017 16:20:01 -0000 1.32 +++ management.html 26 Nov 2017 10:03:03 -0000 @@ -14,9 +14,8 @@

If you find a bug, but you are not fixing it (yet):

    -
  1. Create a (minimal) testcase and file a bug report including it to -our bug tracker.
    2. -
  2. Enter the version number of the compiler in the Known To +
  3. Create a (minimal) testcase and file a bug report. +
  4. Enter the version number of GCC in the Known To Fail field. If you are reporting the bug against a release branch, or the trunk, enter the version number of the next planned release from that branch.