From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: Workflow to accumulate individual changes? Date: Thu, 31 Dec 2009 13:20:18 +0100 Message-ID: References: <87637of4y8.fsf@kobe.laptop> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1262262063 9240 80.91.229.12 (31 Dec 2009 12:21:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 31 Dec 2009 12:21:03 +0000 (UTC) Cc: Giorgos Keramidas , Emacs developers To: Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 31 13:20:55 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 1NQK1L-0008Nq-HU for ged-emacs-devel@m.gmane.org; Thu, 31 Dec 2009 13:20:52 +0100 Original-Received: from localhost ([127.0.0.1]:52104 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NQK1L-0004Uv-PC for ged-emacs-devel@m.gmane.org; Thu, 31 Dec 2009 07:20:51 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NQK1E-0004Ue-FR for emacs-devel@gnu.org; Thu, 31 Dec 2009 07:20:44 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NQK1A-0004Tz-Cf for emacs-devel@gnu.org; Thu, 31 Dec 2009 07:20:44 -0500 Original-Received: from [199.232.76.173] (port=54480 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NQK1A-0004Tt-9I for emacs-devel@gnu.org; Thu, 31 Dec 2009 07:20:40 -0500 Original-Received: from mail-bw0-f215.google.com ([209.85.218.215]:32811) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NQK19-0003Di-Vd for emacs-devel@gnu.org; Thu, 31 Dec 2009 07:20:40 -0500 Original-Received: by bwz7 with SMTP id 7so8821185bwz.26 for ; Thu, 31 Dec 2009 04:20:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=4W+h5Xu6mF+7IpwTniNI5+wkAfCkuXx76Q4qMfOsMVc=; b=wj46zgpGiUb4tr+REVFkqXHYW1NIPvNfx3vv1JcwAtrV6CQP8+cqGlERQJwu5ltIBM 3OqwryIZDUSykXclEoxyrF0WIGrX4zBlRMe0TRC+3Qlu/6cMVob2Oqamk26ZYRUUBBP1 RlBDso1sTo7sW9J4jeMwpDXE3vgnHpUYKGUk8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=RQNEHKPMxJlVVF2r4eFbVLv8I8K5mTbFjs9yjyNQPVp3C6oqTH6vWsLq1tFFG8SwYH RXZ2CWymRbNyCo8JZnhsO7hbkmoGyAPnw4msbAkVguJ8esosmgIDcYCulK0TJoDwyf5d wg6dtcpsMWUhkfsNyyRmyXEirLrG8zttNyrto= Original-Received: by 10.204.152.27 with SMTP id e27mr7319335bkw.192.1262262038186; Thu, 31 Dec 2009 04:20:38 -0800 (PST) In-Reply-To: X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:119141 Archived-At: On Thu, Dec 31, 2009 at 10:21, Andreas Schwab wrote= : > ChangeLog entries and commit messages serve a different purpose. > ChangeLog entries describe the "physical" changes, a commit message the > "logical" change. =C2=A0That is, the commit message describes the changes= et > on a higher level than the ChangeLog entries. =C2=A0As such it does not m= ake > sense to repeat the ChangeLog entries in the commit message. We have plenty of ChangeLog entries that describe both, because it is (or it was, with CVS) much easier/faster to look at the ChangeLog than the cvs log. And most projects do survive withouth ChangeLogs, by using the commit logs, and having a good interface to the VCS to make the diffs easy to access. I think your distinction is theoretically sound, but as a policy difficult to implement. Juanma