From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Workflow to accumulate individual changes? Date: Thu, 31 Dec 2009 15:08:35 +0100 Organization: Organization?!? Message-ID: <87k4w32q3g.fsf@lola.goethe.zz> References: <87637of4y8.fsf@kobe.laptop> <87oclfdzs2.fsf@kobe.laptop> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1262268566 25610 80.91.229.12 (31 Dec 2009 14:09:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 31 Dec 2009 14:09:26 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 31 15:09:20 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NQLiJ-0001Mw-Pl for ged-emacs-devel@m.gmane.org; Thu, 31 Dec 2009 15:09:20 +0100 Original-Received: from localhost ([127.0.0.1]:52527 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NQLiK-0007OF-88 for ged-emacs-devel@m.gmane.org; Thu, 31 Dec 2009 09:09:20 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NQLiF-0007O7-BZ for emacs-devel@gnu.org; Thu, 31 Dec 2009 09:09:15 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NQLiA-0007N2-Q5 for emacs-devel@gnu.org; Thu, 31 Dec 2009 09:09:15 -0500 Original-Received: from [199.232.76.173] (port=42107 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NQLiA-0007Mz-Jc for emacs-devel@gnu.org; Thu, 31 Dec 2009 09:09:10 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:51458) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NQLiA-0005qw-Bm for emacs-devel@gnu.org; Thu, 31 Dec 2009 09:09:10 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1NQLhy-0001G3-P7 for emacs-devel@gnu.org; Thu, 31 Dec 2009 15:08:58 +0100 Original-Received: from p5b2c3a13.dip.t-dialin.net ([91.44.58.19]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 31 Dec 2009 15:08:58 +0100 Original-Received: from dak by p5b2c3a13.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 31 Dec 2009 15:08:58 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 40 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: p5b2c3a13.dip.t-dialin.net X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.90 (gnu/linux) Cancel-Lock: sha1:5dicKWFoz5kl9nMVo+L3mguu5ME= X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:119153 Archived-At: Giorgos Keramidas writes: > I think it's very useful to see file changes in the ChangeLog. It > helps a lot when an Emacs user downloads a tarball of the sources from > the FTP site, because file changes are visible without full access to > the original branch itself or access to a bzr client. _IF_ the file change history is important, we can generate it on the source web page on the fly, from the VCS logs. ChangeLog dates from a time of VCS-less development. If we really want to distribute this sort of info, generating it from commits is quite more reliable. One point of a distributed version control system is that non-privileged users may clone their own repository and have all this historical data in case they need to work with it. My vote is for moving ChangeLog maintenance to proper commit message maintenance: that is more important for a developer with version control access, and again, DVCS use means that this info is available off-line to the user/programmer. With CVS, it wasn't. > Maybe we can try to strike a balance between not keeping the ChangeLog > up to date at all and making it difficult to commit *one* changeset > that includes both ChangeLog updates _and_ file updates by committing > the ChangeLog updates separately? I don't consider it useful anymore to artificially split relevant change info between ChangeLog and commit messages: all relevant version control tools (graphical browsers etc) access the commit messages, and those are there also offline. There is no info we want in ChangeLog that should be missing from commit messages. The price Emacs developers pay for following the proposed hair-splitting policies now is too high. With CVS, off-line access to the ChangeLog was a somewhat valid argument. With DVCS, it isn't. -- David Kastrup