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: Is it time to drop ChangeLogs? Date: Wed, 9 Mar 2016 10:24:33 -0800 Organization: UCLA Computer Science Department Message-ID: <56E06A61.4040508@cs.ucla.edu> References: <56BE7E37.3090708@cs.ucla.edu> <4hd1rw1ubr.fsf@fencepost.gnu.org> <83vb50wxhv.fsf@gnu.org> <87y49vz4cg.fsf@acer.localhost.com> <64a52598-ad53-498c-993c-67d7827dbdfc@default> <838u1uuuau.fsf@gnu.org> <878u1um2xl.fsf@thinkpad.rath.org> <87fuw090k7.fsf@wanadoo.es> <83y49spuxt.fsf@gnu.org> <87pov4achc.fsf@acer.localhost.com> <83r3fkpb3u.fsf@gnu.org> <8337rzpps8.fsf@gnu.org> 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 1457547913 12192 80.91.229.3 (9 Mar 2016 18:25:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 9 Mar 2016 18:25:13 +0000 (UTC) Cc: ofv@wanadoo.es, i.lohmar@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii , John Wiegley Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 09 19:25:00 2016 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 1adin5-0007by-Mu for ged-emacs-devel@m.gmane.org; Wed, 09 Mar 2016 19:24:59 +0100 Original-Received: from localhost ([::1]:43370 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adin5-0001Ic-2o for ged-emacs-devel@m.gmane.org; Wed, 09 Mar 2016 13:24:59 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52601) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adimq-0001IK-Ut for emacs-devel@gnu.org; Wed, 09 Mar 2016 13:24:46 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1adimo-0005q8-Pt for emacs-devel@gnu.org; Wed, 09 Mar 2016 13:24:44 -0500 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:44446) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adimi-0005pF-4W; Wed, 09 Mar 2016 13:24:36 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 6E947160E8D; Wed, 9 Mar 2016 10:24:35 -0800 (PST) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 7QZrj10sFNY8; Wed, 9 Mar 2016 10:24:34 -0800 (PST) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 5413B160F68; Wed, 9 Mar 2016 10:24:34 -0800 (PST) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ycwWVeEO68D3; Wed, 9 Mar 2016 10:24:34 -0800 (PST) Original-Received: from penguin.cs.ucla.edu (Penguin.CS.UCLA.EDU [131.179.64.200]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 39BCC160E8D; Wed, 9 Mar 2016 10:24:34 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 In-Reply-To: <8337rzpps8.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 131.179.128.68 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:201271 Archived-At: On 03/09/2016 08:41 AM, Eli Zaretskii wrote: >> From: John Wiegley >> ... we have only a few needs. If I've understood >> incorrectly, please let me know, as this thread has wandered in a few places. >> >> 1. We need a way to ensure quality commit messages from contributors. This boils down to applying social pressure, one way or another, regardless of the technical details about how ChangeLog entries are recorded. >> 2. We'd like to be able to correct commit messages after the fact. >> 3. We need a convenient way to both create and access this information. >> 4. We want to publish the history of these commit messages in the tarball. >> >> The ChangeLog file and its format are one implementation of these needs that >> has worked over the years. Are you saying that if we move to something else, >> and it fulfills these criteria, you'd be just as happy with it? > Yes. > > However, putting on my system engineer hat, let me make sure the list > of requirements covers all the aspects: > > 5. The "history of commit messages" produced in 4 above should > resemble a ChangeLog file (ideally, it should use the same > format). > 6. The solution should allow manual generation of the "history" file > mentioned in 4, on demand, in reasonably short time, even if the > repo clone does not include a built Emacs. (It is okay to use the > installed Emacs binary, if necessary.) > 7. The solution should support Git workflows we allow: merging > between branches, rebasing local changes on upstream, > cherry-picking from another branch, reverting a commit, tagging a > commit, and amending an unpushed commit. "Support" here means > that the solution should not impose limitations on these > workflows, and the steps for updating whatever databases the > solution will use should not require additional manual work as > result of using these workflows. > The coreutils-like approach that I recently proposed should satisfy requirements (2) through (7). See: https://lists.gnu.org/archive/html/emacs-devel/2016-03/msg00391.html