Re: RFC: documenting all gdb-7.6 branch patches

[Sergio Durigan Junior <sergiodj at redhat dot com>]

On Wednesday, May 08 2013, Joel Brobecker wrote:

> as briefly discussed a few months ago, I would like all patches
> that are applied to the branch to be documented somewhere. The
> purpose of this document would be for me to have something I can
> simply copy/paste when I announce the minor/corrective release.
> So far, I have been going through each and every patch, trying
> to figure out what the intent was, but this is very time consuming
> and not always accurate.

I committed a patch yesterday fixing a PR, but used the infamous
"ChangeLog entry" as the commit message.  I've been trying to avoid
doing this, but this time I bit my tongue...  So sorry.

> My proposal of using the NEWS file had a rather tepid reaction,
> so I am proposing instead that we use the GDB 7.6 release wiki page.
> I can add a section at the top of the page listing the changes applied
> since the GDB 7.6 release, and explaining their effect and why they
> matter to the user.

Either way is fine by me, really.

> 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.
>
> Would that be a workable approach? Once we agree on a protocol,
> I will go back and ask the authors of patches already ported to
> the branch to supply the description.

Yes, that sounds a good approach, thanks.  I will wait until we reach a
consensus before I send the description to the patch I pushed.

Thanks,

-- 
Sergio