From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15451 invoked by alias); 2 Feb 2018 15:23:54 -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 15434 invoked by uid 89); 2 Feb 2018 15:23:53 -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,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy= 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; Fri, 02 Feb 2018 15:23:52 +0000 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ehdAr-0000UU-7m for gdb-patches@sourceware.org; Fri, 02 Feb 2018 10:23:51 -0500 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:47404) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ehdAq-0008J4-Th; Fri, 02 Feb 2018 10:22:45 -0500 Received: from [176.228.60.248] (port=3462 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1ehWnf-00011a-Nm; Fri, 02 Feb 2018 03:34:24 -0500 Date: Fri, 02 Feb 2018 15:23:00 -0000 Message-Id: <837erveqnz.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 21:32:13 +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> <83mv0sehrq.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/msg00033.txt.bz2 > From: Yao Qi > Date: Thu, 1 Feb 2018 21:32:13 +0000 > Cc: Simon Marchi , GDB Patches > > > 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. > > > > Yes, do we want to change the rule of writing ChangeLog, so that > we can/should put the motivation for the change? Is the motivation > mandatory in the changelog or optional? > > >> 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? > > We need a clear rule on writing changelog, otherwise how do we > write changelog or review patches? I agree. I hope Someone(TM) will answer these questions.