From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-517911-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 104318 invoked by alias); 21 Jan 2020 15:40:49 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
Received: (qmail 104278 invoked by uid 89); 21 Jan 2020 15:40:49 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-6.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Languages-Length:939
X-HELO: foss.arm.com
Received: from foss.arm.com (HELO foss.arm.com) (217.140.110.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 21 Jan 2020 15:40:39 +0000
Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14])	by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id A910B30E;	Tue, 21 Jan 2020 07:40:37 -0800 (PST)
Received: from e120077-lin.cambridge.arm.com (e120077-lin.cambridge.arm.com [10.2.78.81])	by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 038CB3F52E;	Tue, 21 Jan 2020 07:40:36 -0800 (PST)
Subject: Re: [PATCH, v2] wwwdocs: e-mail subject lines for contributions
To: Jakub Jelinek <jakub@redhat.com>
Cc: Gerald Pfeifer <gerald@pfeifer.com>, gcc-patches@gcc.gnu.org, GCC Development <gcc@gcc.gnu.org>
References: <c3928f40-2d71-fb5b-f2e0-3878ac88a2b7@arm.com> <alpine.LSU.2.21.2001191425160.739@anthias.pfeifer.com> <353faf3e-bf43-eb4d-542d-45a53dce77b2@arm.com> <ff130918-cbbb-2afc-d752-1af2ca9df340@arm.com> <20200121150440.GX10088@tucnak> <b31c83f8-c231-d28a-9f4c-ae5e5d9526b1@arm.com> <20200121153902.GY10088@tucnak>
From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
Message-ID: <d132302d-d09b-aaa6-715a-2e39679883ed@arm.com>
Date: Tue, 21 Jan 2020 16:26:00 -0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <20200121153902.GY10088@tucnak>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2020-01/txt/msg01356.txt.bz2

On 21/01/2020 15:39, Jakub Jelinek wrote:
> On Tue, Jan 21, 2020 at 03:33:22PM +0000, Richard Earnshaw (lists) wrote:
>>> Some examples would be useful I'd say, e.g. it is unclear in what way you
>>> want the PR number to be appended, shall it be
>>> something: whatever words describe it PR12345
>>> or
>>> something: whatever words describe it (PR12345)
>>> or
>>> something: whatever words describe it: PR12345
>>> or
>>> something: whatever words describe it [PR12345]
>>> or something else?
>>
>> Glibc use "[BZ #nnnn]" - obviously BZ becomes PR, but after that, I'm not
>> too worried.  I'd be happy with [PR #nnnn], but if folk want something else,
>> please say so quickly...
> 
> [PR 12345] or [PR #12345] is bad, because the bugzilla won't underline it,
> it needs to be either PR12345 word, or PR component/12345 .
> 
> 	Jakub
> 

ok, lets go with [PRnnnn] then.

R.