From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Generating the ChangeLog files from the commit messages Date: Thu, 20 Nov 2014 12:12:55 -0800 Organization: UCLA Computer Science Department Message-ID: <546E4B47.50506@cs.ucla.edu> References: <21606.10799.112099.788101@a1i15.kph.uni-mainz.de> <1753218.Ot8JCqssfN@descartes> <546AABCF.8030705@cs.ucla.edu> <9xioico2nm.fsf@fencepost.gnu.org> <83k32s9zm5.fsf@gnu.org> <546BC2C6.50909@cs.ucla.edu> <546D3287.7070802@cs.ucla.edu> <546D5CBA.2010200@cs.ucla.edu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1416514423 28198 80.91.229.3 (20 Nov 2014 20:13:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 20 Nov 2014 20:13:43 +0000 (UTC) Cc: Emacs developers To: Yuri Khan Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 20 21:13:36 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XrY6i-0003LT-BR for ged-emacs-devel@m.gmane.org; Thu, 20 Nov 2014 21:13:36 +0100 Original-Received: from localhost ([::1]:37191 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XrY6h-000843-ST for ged-emacs-devel@m.gmane.org; Thu, 20 Nov 2014 15:13:35 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46528) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XrY6M-0007vf-NL for emacs-devel@gnu.org; Thu, 20 Nov 2014 15:13:22 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XrY6E-0005eS-7i for emacs-devel@gnu.org; Thu, 20 Nov 2014 15:13:14 -0500 Original-Received: from smtp.cs.ucla.edu ([131.179.128.62]:45691) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XrY6E-0005e6-1u for emacs-devel@gnu.org; Thu, 20 Nov 2014 15:13:06 -0500 Original-Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 8390BA600F4; Thu, 20 Nov 2014 12:13:04 -0800 (PST) X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu Original-Received: from smtp.cs.ucla.edu ([127.0.0.1]) by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3DOr9cDrs9cI; Thu, 20 Nov 2014 12:12:55 -0800 (PST) Original-Received: from penguin.cs.ucla.edu (Penguin.CS.UCLA.EDU [131.179.64.200]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id CFECEA600FE; Thu, 20 Nov 2014 12:12:55 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 131.179.128.62 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:177889 Archived-At: On 11/19/2014 08:04 PM, Yuri Khan wrote: > What is the existing practice for such cases? Existing practice elsewhere is to have just one generated ChangeLog file, at the top level. If we had done this for Emacs from day one, we'd have a ChangeLog file of about 25 MB. Although this would have been too large in the old days, nowadays it's not such a big deal, as computers typically have way more than 25 MB. When I open a 25 MB ChangeLog file with Emacs, it appears instantaneously on my screen, and I can navigate through it without delays. I prefer having a single ChangeLog file to having smaller ChangeLog* files in various locations, as it's a bit easier to scout through history that way. The patch that I've proposed in Bug#19113 doesn't go that far, though; it merely arranges for future git commit messages to be copied into the top-level ChangeLog. Perhaps coalescing the historical ChangeLog files could be done in a followon patch.