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: Joel Brobecker <brobecker at adacore dot com>
- To: Doug Evans <dje at google dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 3 Dec 2012 13:16:10 +0400
- Subject: Re: proposal for branch patches after first release
- References: <20121129141415.GJ3540@adacore.com> <CADPb22SfmVBP4s=X04hN7UP7LpHyN0iuUn=RRsDQkd-2zaonrw@mail.gmail.com>
> If it were me I'd just diff the ChangeLogs, write something based on
> that (but not worry about being too detailed if it'll take too much
> time to dig deeper), require bug numbers or whatever to be in the
> ChangeLogs, and leave it at that.
In practice, many patches are often difficult to gauge, at least for me.
So this would be noticeably affecting the quality of the announcement,
to the point where I'd ask myself whether there might be any point in
going through the exercise at all.
All I need is a little help from the person the author, by ways of
a note, somewhere, explaining what it does. It doesn't matter as much
where the information is. It can be a "release notes" file, or even
the wiki. To me, it seems better to keep that information inside the
GDB sources, so I'd personally go with that.
--
Joel