From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Should we restore manually maintained ChangeLogs Date: Tue, 08 Mar 2016 18:19:16 +0200 Message-ID: <8360wxrlh7.fsf@gnu.org> References: <56BE7E37.3090708@cs.ucla.edu> <4hd1rw1ubr.fsf@fencepost.gnu.org> <83vb50wxhv.fsf@gnu.org> <87y49vz4cg.fsf@acer.localhost.com> <87vb4zb0i4.fsf@gnu.org> <837fheuu6a.fsf@gnu.org> <83twkiteb3.fsf@gnu.org> <83lh5utbxb.fsf@gnu.org> <56DDD02A.20809@cs.ucla.edu> <83fuw2t2ue.fsf@gnu.org> <56DE0F6A.6010207@cs.ucla.edu> <87y49tdq33.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1457453972 6816 80.91.229.3 (8 Mar 2016 16:19:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 8 Mar 2016 16:19:32 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 08 17:19:31 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 1adKM6-0007yr-7r for ged-emacs-devel@m.gmane.org; Tue, 08 Mar 2016 17:19:30 +0100 Original-Received: from localhost ([::1]:35622 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adKM5-00074B-Hn for ged-emacs-devel@m.gmane.org; Tue, 08 Mar 2016 11:19:29 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42411) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adKLo-00073m-BT for emacs-devel@gnu.org; Tue, 08 Mar 2016 11:19:13 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1adKLk-0005Uy-FN for emacs-devel@gnu.org; Tue, 08 Mar 2016 11:19:12 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:42318) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adKLk-0005Uo-C6; Tue, 08 Mar 2016 11:19:08 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2722 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1adKLi-0003iO-Sx; Tue, 08 Mar 2016 11:19:07 -0500 In-reply-to: (message from Stefan Monnier on Tue, 08 Mar 2016 10:15:35 -0500) 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-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:201166 Archived-At: > From: Stefan Monnier > Date: Tue, 08 Mar 2016 10:15:35 -0500 > > >> I'd rather just do what coreutils, grep, tar, etc. use. It's just as > > I like what is done by those projects. However they don't have a merge > > workflow. I agree with you that for Emacs release branches, maintaining > > ChangeLog manually seems reasonable. However how will it work for the > > feature branches which are meant to be merge sooner or later? > > The ChangeLog would only be generated into tarballs (i.e. only when > leaving the realm of the VCS), so they just never appear on any branch. Which means they will either have all the uncorrected mistakes (like missing "tiny change" etc.), or you expect from Someone to do all the fixes as part of tarring a release. I think both alternatives are unacceptable.