From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-109354-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 13931 invoked by alias); 15 Jan 2014 19:45:35 -0000
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
Received: (qmail 13912 invoked by uid 89); 15 Jan 2014 19:45:34 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2
X-Spam-User: qpsmtpd, 2 recipients
X-HELO: mx1.redhat.com
Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 15 Jan 2014 19:45:34 +0000
Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25])	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s0FJjTh4027606	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);	Wed, 15 Jan 2014 14:45:29 -0500
Received: from barimba (ovpn-113-85.phx2.redhat.com [10.3.113.85])	by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s0FJjR9A007100	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);	Wed, 15 Jan 2014 14:45:28 -0500
From: Tom Tromey <tromey@redhat.com>
To: Cary Coutant <ccoutant@google.com>
Cc: Joel Brobecker <brobecker@adacore.com>, Binutils <binutils@sourceware.org>,        gdb-patches <gdb-patches@sourceware.org>
Subject: Re: small request regarding commits in binutils-gdb.git
References: <20140115121251.GM4639@adacore.com>	<CAHACq4o_L+s_U2ew-2emAAKLFXYRrrVhc_ozeO3icynNNNYK1A@mail.gmail.com>
Date: Wed, 15 Jan 2014 19:45:00 -0000
In-Reply-To: <CAHACq4o_L+s_U2ew-2emAAKLFXYRrrVhc_ozeO3icynNNNYK1A@mail.gmail.com>	(Cary Coutant's message of "Wed, 15 Jan 2014 11:31:24 -0800")
Message-ID: <87y52howq0.fsf@fleche.redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-SW-Source: 2014-01/txt/msg00556.txt.bz2

>>>>> "Cary" == Cary Coutant <ccoutant@google.com> writes:

>> For the rest of the community, using a meaningful subject, one that
>> actually gives a hint at what it does, is something that I have
>> found to be really helpful. For instance, "Provide format string
>> to as_warn" can be more helpful when scanning through a list
>> of commits than "PR gas/16434".

Cary> This is all good, but could you clarify what the conventions are now
Cary> for where the "PR gas/16434" needs to go in order for the patch to get
Cary> sent to bugzilla?

It will work as long as it appears anywhere in the commit message.

Tom