From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 120111 invoked by alias); 6 Feb 2018 21:02:42 -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 120092 invoked by uid 89); 6 Feb 2018 21:02:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=reflection, Hx-languages-length:1849 X-Spam-User: qpsmtpd, 2 recipients X-HELO: 9pmail.ess.barracuda.com Received: from 9pmail.ess.barracuda.com (HELO 9pmail.ess.barracuda.com) (64.235.150.225) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 06 Feb 2018 21:02:40 +0000 Received: from MIPSMAIL01.mipstec.com (mailrelay.mips.com [12.201.5.28]) by mx29.ess.sfj.cudaops.com (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NO); Tue, 06 Feb 2018 21:02:18 +0000 Received: from [10.20.78.193] (10.20.78.193) by mips01.mipstec.com (10.20.43.31) with Microsoft SMTP Server id 14.3.361.1; Tue, 6 Feb 2018 12:58:43 -0800 Date: Tue, 06 Feb 2018 21:02:00 -0000 From: "Maciej W. Rozycki" To: Yao Qi CC: GDB , GDB Patches Subject: Re: Stop updating ChangeLog? In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-BESS-ID: 1517950937-637139-15136-245233-5 X-BESS-VER: 2018.1-r1801291959 X-BESS-Apparent-Source-IP: 12.201.5.28 X-BESS-Outbound-Spam-Score: 0.00 X-BESS-Outbound-Spam-Report: Code version 3.2, rules version 3.2.2.189737 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------- 0.00 BSF_BESS_OUTBOUND META: BESS Outbound X-BESS-Outbound-Spam-Status: SCORE=0.00 using account:ESS59374 scores of KILL_LEVEL=7.0 tests=BSF_BESS_OUTBOUND X-BESS-BRTS-Status:1 X-SW-Source: 2018-02/txt/msg00097.txt.bz2 Hi Yao, > #1 Are ChangeLog files useful in GDB releases to various people > who build GDB releases? > #2 Are ChangeLog files useful in GDB repo to various GDB > developers? > > a) If answers are Yes/Yes, we keep unchanged, > b) If answers are No/No, we don't need to write changelog entries in > git commit log, nor updating ChangeLog file, > c) If answer are Yes/No, developers still have to write changelog > entries in git commit log, and we can generate ChangeLog on > release from git log. > d) If answers are No/Yes, get use to git to get the information from > git log instead of ChangeLog, For me it's No/Yes for two reasons: 1. It is often cheaper in terms of computation or I/O to run `grep' on local ChangeLog files than on output from `git', which in turn means you get results sooner. I know it's a weak argument, but still. 2. More importantly, many times I found writing a ChangeLog entry the last reflection point when I realised the solution wasn't actually the right one. This is because at that point you need to give individual changes another thought, and then actually look at them from a different angle, to have them properly expressed in ChangeLog-speak. I expect that at least some people have had a similar experience and I'd like to keep that opportunity. I reckon we had a discussion before (at the last GNU Tools Cauldron perhaps?) where we concluded that we ought to work towards having a GIT commit hook extracting embedded ChangeLog entries from the commit description and adding them to actual ChangeLog files automagically. I would be in favour to that. Although myself I have developed a work flow which makes pasting ChangeLog entries into files from a commit description very little involving, I still find ChangeLog file conflicts a problem with backports. FWIW, Maciej