From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 95080 invoked by alias); 1 Feb 2018 17:33:53 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 95064 invoked by uid 89); 1 Feb 2018 17:33:52 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,KAM_SHORT,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=rigid, lax X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (208.118.235.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 01 Feb 2018 17:33:51 +0000 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ehIk5-0003JI-Vl for gdb-patches@sourceware.org; Thu, 01 Feb 2018 12:33:50 -0500 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:50462) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ehIk5-0003Iv-Rr; Thu, 01 Feb 2018 12:33:45 -0500 Received: from [176.228.60.248] (port=1774 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1ehIk5-0002Ar-8h; Thu, 01 Feb 2018 12:33:45 -0500 Date: Thu, 01 Feb 2018 17:33:00 -0000 Message-Id: <83mv0sehrq.fsf@gnu.org> From: Eli Zaretskii To: Yao Qi CC: simon.marchi@ericsson.com, gdb-patches@sourceware.org In-reply-to: (message from Yao Qi on Thu, 1 Feb 2018 16:51:36 +0000) Subject: Re: [ANNOUNCEMENT] GDB 8.1 release branch created! Reply-to: Eli Zaretskii References: <83h8rlyakm.fsf@gnu.org> <83lggvupt6.fsf@gnu.org> <83lgglnadl.fsf@gnu.org> <83fu6sln4o.fsf@gnu.org> <3d75778f-5c91-5680-b9fa-c2f2c902ff67@ericsson.com> <838tcklaev.fsf@gnu.org> <83607njlsh.fsf@gnu.org> <86wozwbv68.fsf@gmail.com> <83shakeku7.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-IsSubscribed: yes X-SW-Source: 2018-02/txt/msg00020.txt.bz2 > From: Yao Qi > Date: Thu, 1 Feb 2018 16:51:36 +0000 > Cc: Simon Marchi , GDB Patches > > On Thu, Feb 1, 2018 at 4:27 PM, Eli Zaretskii wrote: > > Maybe I'm missing something, but isn't the commit log entry supposed > > to have the same text as the ChangeLog for that change? > > My understanding is that ChangeLog entry should be copied at the end > of commit log I believe I did that, except that I moved the motivation for the change before the ChangeLog header, as it belongs to the preamble of the Git log. (In ChangeLog, there's no subdivision of the entry.) > > And what's wrong with having error messages in ChangeLog's, anyway? > > Each entry in ChangeLog describes the changes to the code, > https://www.gnu.org/prep/standards/standards.html#Change-Log-Concepts > IMO, error messages are out of the scope of what ChangeLog is intended > to describe. This is changing, and some GNU projects already do it differently. I believe the next version of standards.texi will change the recommendations to be more lax. And using different style for each project is a pain. Is GDB really so rigid as to not tolerate this? Please note that the error message I cited is just part of the motivation for the change, so we are really talking about including the motivation in the ChangeLog. > Also, I've never seen such ChangeLog entry (with error messages) > before. That's not necessarily a reason for rejecting such entries. So: what is the project's take on this, if there is one?