This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: ChangeLog's: do we have to?
- From: Segher Boessenkool <segher at kernel dot crashing dot org>
- To: Trevor Saunders <tbsaunde at tbsaunde dot org>
- Cc: "Maciej W. Rozycki" <macro at linux-mips dot org>, Tom Tromey <tom at tromey dot com>, Florian Weimer <fw at deneb dot enyo dot de>, Paul Koning <paulkoning at comcast dot net>, Aldy Hernandez <aldyh at redhat dot com>, GCC Mailing List <gcc at gcc dot gnu dot org>, Jakub Jelinek <jakub at redhat dot com>
- Date: Wed, 1 Aug 2018 09:24:29 -0500
- Subject: Re: ChangeLog's: do we have to?
- References: <6f84c126-136e-7f6d-ec69-4775a58610a4@redhat.com> <87r2khg2v8.fsf@mid.deneb.enyo.de> <9702A2D4-9DD3-4985-B804-72F8CD3E6610@comcast.net> <87fu0xg15w.fsf@mid.deneb.enyo.de> <87fu0xmjer.fsf@tromey.com> <alpine.LFD.2.21.1807312350570.4967@eddie.linux-mips.org> <20180801001833.GC6238@ball>
On Tue, Jul 31, 2018 at 08:18:33PM -0400, Trevor Saunders wrote:
> And that's ignoring the much larger amount of busywork involved in
> generating the changelog in the first place which if you follow the GNU
> rules about describing the diff without explaining it is basically by
> definition mechanical.
The changelog *should* describe and explain the patch. It should not
describe or explain why we want this patch and not another.
Segher