This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: proposal for branch patches after first release
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 29 Nov 2012 18:14:10 +0200
- Subject: Re: proposal for branch patches after first release
- References: <20121129141415.GJ3540@adacore.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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.