From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 112471 invoked by alias); 2 Feb 2018 15:53:17 -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 111519 invoked by uid 89); 2 Feb 2018 15:53:16 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=pros, price, Hx-languages-length:1405, pay X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 02 Feb 2018 15:53:15 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id E6C48564DE; Fri, 2 Feb 2018 10:53:13 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id QBbd4Qd1Kbys; Fri, 2 Feb 2018 10:53:13 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id A5E49562CC; Fri, 2 Feb 2018 10:53:12 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 284A483307; Fri, 2 Feb 2018 19:53:08 +0400 (+04) Date: Fri, 02 Feb 2018 15:53:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: Yao Qi , simon.marchi@ericsson.com, gdb-patches@sourceware.org Subject: Re: [ANNOUNCEMENT] GDB 8.1 release branch created! Message-ID: <20180202155308.vx7hkemrjfmb27mn@adacore.com> References: <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> <837erveqnz.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <837erveqnz.fsf@gnu.org> User-Agent: NeoMutt/20170113 (1.7.2) X-SW-Source: 2018-02/txt/msg00035.txt.bz2 > > 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. Well, if it were me, I would stop using ChangeLog files with immediate effect. The purpose of ChangeLog files, as I understand it, is to describe the "what changed", and is aimed at people who download a given release and want to know what changed (because they do not have access to the version control information). While the above might have been essential 20 or 25 years ago, it is trivial for anyone today to have access to the change history of our program. Two options: - git clone our public repository; or... - ... if they don't want to use git, they can use the gitweb interface. I think that this is an acceptable way for us to provide the log of changes that were made. Currently, the situation is that we all pay a price in term of time wasted populating those files, and when we add the time collectively spent on those, I cannot imagine the few people's convenience would be worth that much effort. I vote for we stop using those ChangeLog files right now. We can still have them as part of the ChangeLog if people want -- although, I am also open to considering the pros and cons of keeping it, but I think they might not be worth the investiment either. -- Joel