From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Danjou Subject: Re: Re: A request: Moving away from ChangeLog Date: Fri, 21 May 2010 23:17:22 +0200 Message-ID: <87zkzt550d.fsf@keller.adm.naquadah.org> References: <2151275B-C80E-4B40-9022-8C9054020163@gmail.com> <871vd5dkqu.fsf@saadawi.sbszh.ch> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1281176300==" Return-path: Received: from [140.186.70.92] (port=51655 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OFZb0-0002Y9-4R for emacs-orgmode@gnu.org; Fri, 21 May 2010 17:17:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OFZay-0000gQ-BV for emacs-orgmode@gnu.org; Fri, 21 May 2010 17:17:29 -0400 Received: from prometheus.naquadah.org ([212.85.154.174]:39905 helo=mx1.naquadah.org) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OFZay-0000fq-2c for emacs-orgmode@gnu.org; Fri, 21 May 2010 17:17:28 -0400 In-Reply-To: <871vd5dkqu.fsf@saadawi.sbszh.ch> (Christian Egli's message of "Fri, 21 May 2010 23:10:17 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Christian Egli Cc: emacs-orgmode@gnu.org --===============1281176300== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Fri, May 21 2010, Christian Egli wrote: > So before pouring out the baby with the bathwater maybe we should at > least try if the git merge driver solves the main problem we have with > the Changelog files.=20=20 This does not resolve a ugly part which is the duplication of information: in the changelog file and in the commit changelog. Documenting commit properly should be enough. A better idea, if you want a user readable changelog, is 2 write the commit message in a parseable format with 2 information: one for the developer (what the commit changes in the code, API, whatever), and one for the user (what it changes in the software usage). That last one only if necessary. And with this, it's a win-win: you can generate changelog files, and you can read changelog while reading commit/bisecting/whatever git action you do. =2D-=20 Julien Danjou // =E1=90=B0 http://julien.danjou.info --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkv2+GIACgkQpGK1HsL+5c201gCfcv+/xxRMuxcAUrbp/Azmxbib 15wAoKDnmzWLzGRWC5fhipWEORC32VdO =eIsF -----END PGP SIGNATURE----- --=-=-=-- --===============1281176300== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode --===============1281176300==--