This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFC: documenting all gdb-7.6 branch patches
- From: Pedro Alves <palves at redhat dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 10 May 2013 15:05:36 +0100
- Subject: Re: RFC: documenting all gdb-7.6 branch patches
- References: <20130508052420 dot GR5278 at adacore dot com> <518A8C8F dot 9050608 at redhat dot com> <20130510122618 dot GH9160 at adacore dot com>
On 05/10/2013 01:26 PM, Joel Brobecker wrote:
>> I agree. The wiki is a good place for this.
>>
>>> Additionally, I'd like the description to be reviewed on gdb-patches
>>> before the patch is ported to the branch, and the description is added
>>> to the list.
>>
>> That's fine with me.
>
> Looks like I might just grab the "champion's" spot from right under
> Pedro's nose :-).
Super! :-)
> For the sake of discussion, and to show what the result would look
> like, here is the entry I just added:
> (see: http://sourceware.org/gdb/wiki/GDB_7.6_Release)
>
>> Fixes in GDB 7.6.1
>> ------------------
>>
>> GDB 7.6.1 brings the following fixes and improvements:
>>
>> * PR tdep/15420 (Cannot debug threaded programs on newer versions
>> of x86-solaris - Solaris 10, Update 10 or later)
>
> Does it look sufficiently detailed for publication in the annoucement
> email, when we publich 7.6.1?
That looks fine to me.
>> For bug fixes, it'll probably be good to make sure there's always a
>> PR in bugzilla to point at, even if we still give a short description
>> of the bug in the release notes in addition to the PR number / link.
>
> OK for me.
(We may later end up finding out that all we put in minor point
releases is bugfixes, so that putting a "gdb-7.6.1" keyword in
the PRs themselves that would allow easy querying would
dispense the wiki process. :-) Let's see how this goes.)
--
Pedro Alves