From patchwork Mon Apr 20 10:57:13 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Tom de Vries X-Patchwork-Id: 462770 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org 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 40CF91400DE for ; Mon, 20 Apr 2015 20:57:48 +1000 (AEST) Authentication-Results: ozlabs.org; dkim=pass reason="1024-bit key; unprotected key" header.d=gcc.gnu.org header.i=@gcc.gnu.org header.b=bJKUefKJ; dkim-adsp=none (unprotected policy); dkim-atps=neutral DomainKey-Signature: a=rsa-sha1; c=nofws; d=gcc.gnu.org; h=list-id :list-unsubscribe:list-archive:list-post:list-help:sender :message-id:date:from:mime-version:to:cc:subject:content-type; q=dns; s=default; b=Mgi/OS5nJYjt5Dc7Xwcjp3Foj/mQnjXRM+awWGHDHUq ILvW0oQQOPQeJZlolHHNa+EGfz+TkQE76rgUFmxl/M0GtZba2GXX4LdiKA5H1Qdo Ujz/vVe3fPmMIJFnxSbxbJQWkgytEoQ7TEk/hC+YivFlIv4gptnSAOtwjMjKwoaQ = 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 :message-id:date:from:mime-version:to:cc:subject:content-type; s=default; bh=wkXMHCkvCpA1lyzuQ+CcjdJlsJU=; b=bJKUefKJWJoOiNeeG zbuktLtyaPt8qdE84FZ/gxL/uACJp0S/xiJodkZiO1vbMplIWhhiycu4RsoZFnlc 4y4b8pBfwurhbir3b1sjUp2I4zZ1Thc+/6gfn/C9pohs82sNtKMeyLBLm0AuF9eb X241VtYb7oFSK9Ygs42VnyAgHk= Received: (qmail 114659 invoked by alias); 20 Apr 2015 10:57:41 -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 114648 invoked by uid 89); 20 Apr 2015 10:57:40 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL, BAYES_00, RCVD_IN_DNSWL_LOW, SPF_PASS autolearn=ham version=3.3.2 X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 20 Apr 2015 10:57:39 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=SVR-IES-FEM-01.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1Yk9OR-00071D-8e from Tom_deVries@mentor.com ; Mon, 20 Apr 2015 03:57:35 -0700 Received: from [127.0.0.1] (137.202.0.76) by SVR-IES-FEM-01.mgc.mentorg.com (137.202.0.104) with Microsoft SMTP Server id 14.3.224.2; Mon, 20 Apr 2015 11:57:16 +0100 Message-ID: <5534DB89.6000200@mentor.com> Date: Mon, 20 Apr 2015 12:57:13 +0200 From: Tom de Vries User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: GCC Patches CC: Ian Lance Taylor Subject: [RFC][wwwdocs] bug report reopen policy Hi, In PR64683 comment 11, Ian mentioned: ... This bug may have the same symptoms but it has a completely different cause. Next time, please do not reopen the bug unless you are certain it has the same cause. Please open a new bug instead. Thanks. ... I couldn't find a similar rule in the 'Reporting Bugs' section, so this patch adds such a rule. The patch (validated as required) adds the following item to the 'Reporting Bugs - What we DON'T want' bit of https://gcc.gnu.org/bugs/ : ... * Reopening a bug report when you're not certain that the failure you're reporting has the same root cause as the reopened bug report ... Thanks, - Tom Index: htdocs/bugs/index.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/index.html,v retrieving revision 1.116 diff -u -r1.116 index.html --- htdocs/bugs/index.html 5 Jul 2014 21:52:32 -0000 1.116 +++ htdocs/bugs/index.html 20 Apr 2015 10:46:37 -0000 @@ -119,6 +119,9 @@
  • Questions about the correctness or the expected behavior of certain constructs that are not GCC extensions. Ask them in forums dedicated to the discussion of the programming language
    • + +
  • Reopening a bug report when you're not certain that the failure you're + reporting has the same root cause as the reopened bug report

    • Where to post it