From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-96436-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 12927 invoked by alias); 29 Nov 2012 16:14:00 -0000
Received: (qmail 12908 invoked by uid 22791); 29 Nov 2012 16:13:59 -0000
X-SWARE-Spam-Status: No, hits=-4.5 required=5.0	tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout23.012.net.il (HELO mtaout23.012.net.il) (80.179.55.175)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 29 Nov 2012 16:13:51 +0000
Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0ME900D00BMKPV00@a-mtaout23.012.net.il> for gdb-patches@sourceware.org; Thu, 29 Nov 2012 18:13:49 +0200 (IST)
Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0ME900DHUBR1DCD0@a-mtaout23.012.net.il>; Thu, 29 Nov 2012 18:13:49 +0200 (IST)
Date: Thu, 29 Nov 2012 16:14:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: proposal for branch patches after first release
In-reply-to: <20121129141415.GJ3540@adacore.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83wqx4v12l.fsf@gnu.org>
References: <20121129141415.GJ3540@adacore.com>
X-IsSubscribed: yes
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
X-SW-Source: 2012-11/txt/msg00874.txt.bz2

> Date: Thu, 29 Nov 2012 15:14:15 +0100
> From: Joel Brobecker <brobecker@adacore.com>
> 
> The proposal:
> 
>     Once a release has been published off a branch, any patch merged
>     on the release branch requires a corresponding update in the
>     NEWS file.

That'd be a nuisance, IMO, because some of them might be
NEWS-unworthy.

An alternative would be to require some predictably formatted string
in the log entry or the commit message, which you then could grep for.

Yet another alternative would be to have a separate file, which
doesn't get into the tarball, with the relevant info, and request each
commit to the branch be accompanied with an entry for that file.