From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Karl Fogel Newsgroups: gmane.emacs.devel Subject: Re: Is it time to drop ChangeLogs? Date: Wed, 09 Mar 2016 14:42:30 -0600 Message-ID: <87r3fjtmbt.fsf@red-bean.com> References: <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> <83lh5rps0t.fsf@gnu.org> <56E066BD.5050403@cs.ucla.edu> <87lh5rv7kk.fsf@red-bean.com> <83pov3o62y.fsf@gnu.org> <87bn6nv3yw.fsf@red-bean.com> <838u1ro10g.fsf@gnu.org> Reply-To: Karl Fogel NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1457556192 19164 80.91.229.3 (9 Mar 2016 20:43:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 9 Mar 2016 20:43:12 +0000 (UTC) Cc: eggert@cs.ucla.edu, johnw@gnu.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 09 21:43:07 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 1adkwW-0004ln-V6 for ged-emacs-devel@m.gmane.org; Wed, 09 Mar 2016 21:42:53 +0100 Original-Received: from localhost ([::1]:44385 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adkwW-0004fx-7q for ged-emacs-devel@m.gmane.org; Wed, 09 Mar 2016 15:42:52 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47559) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adkwG-0004fi-9m for emacs-devel@gnu.org; Wed, 09 Mar 2016 15:42:37 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1adkwD-0007Dh-1c for emacs-devel@gnu.org; Wed, 09 Mar 2016 15:42:36 -0500 Original-Received: from mail-ig0-x236.google.com ([2607:f8b0:4001:c05::236]:37993) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adkwC-0007Dd-Qy; Wed, 09 Mar 2016 15:42:32 -0500 Original-Received: by mail-ig0-x236.google.com with SMTP id ig19so1634059igb.1; Wed, 09 Mar 2016 12:42:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:references:reply-to:date:in-reply-to :message-id:user-agent:mime-version; bh=EerpAOjs8IUpn7+dYm3BHDQFR01D7/yGWS2QqvVZWUU=; b=eDMyLnWhXIejFJiKySAkmQhhzM+3YRa9gW7u4PfRGCWsUiyBCSKica/KthwznXfRrP IHOwjvqeA/jtK6X4Nnzry46sywG55XsksQI48UWRQBYbY4nfVazjSiMwpcnV1FpFWuVh eJqZWiKVpBwoSnXHpdrOxMWabcy9Y9iNOwJCkPcK2PSijHYAlm8r77p3ialAEUm9Ol4c BlUs4Ne2l0orF/wGevbuBIyuvB8um2Mh54gIJx2a8P8Giw69OUB1Gc9csPim2VST0EG+ K57QVm5ZK8aEAmOAuLdaESU9/SgHK5KxUwjY9NcHR7XaTncDO13fO4BOuMSoTFWatvSS aGFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:from:to:cc:subject:references:reply-to :date:in-reply-to:message-id:user-agent:mime-version; bh=EerpAOjs8IUpn7+dYm3BHDQFR01D7/yGWS2QqvVZWUU=; b=NGn/37RKg64BH3oesYyz8FHwL6CuQHi8K8CMjFtgyz0jBCcKFSFMrZzzdtfWDw+36N YylYa3RtOn2LSJ6U6ZpSuXSezfXK1t3lS7miejjMjU0Td3O/z+c/aAfuXFtDdNW0+7IM CiJ692tbfQO8s3ZuEJu4LeaLrymS5jlt2E581j9vzrGs+yuqX9dfMTn0mo4IfNntEe7s TSX/EKoqnpyxSOYdkTUdQAn9I2yOAJhwIJ+SV556rkUjN3UERRCu0BXbzmrmEppit9Tp liJEDME4Oh3JgInALbHYsCbt0Y71iF1BDkiao0ERmqvGOEY4WWn+SqvfYqxpIIPKfqQx dxCA== X-Gm-Message-State: AD7BkJK02AGQLX7tjL2LYD0V7QfdsZhcyZiVybCcSyZb5rUegbwmz44tys3xeRbYJYCb+w== X-Received: by 10.50.61.166 with SMTP id q6mr308896igr.96.1457556152166; Wed, 09 Mar 2016 12:42:32 -0800 (PST) Original-Received: from floss (74-92-190-114-Illinois.hfc.comcastbusiness.net. [74.92.190.114]) by smtp.gmail.com with ESMTPSA id o125sm172468ioo.6.2016.03.09.12.42.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Mar 2016 12:42:31 -0800 (PST) In-Reply-To: <838u1ro10g.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 09 Mar 2016 22:21:51 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.92 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:4001:c05::236 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:201318 Archived-At: Eli Zaretskii writes: >I don't even need to explain that: there are already people in this >discussion who said they'd like to use a less formal format. (You >already asked who those people were, and Dmitry already pointed out >who they were.) To me, the connection is very clear. If you don't >see it, just trust the facts -- it is already happening. I've worked in projects where we successfully enforce ChangeLog-style commit message conventions without having actual ChangeLog files. If the Emacs project is having a social problem enforcing conventions, that's certainly something to be solved. But blaming it on the absence of ChangeLog files does not hold up empirically. I do not see any connection between the fact that some people advocate using a less formal format, and the question of whether or not we should have ChangeLog *files*. One is about commit message format (other projects enforce a format successfully, and some even enforce this particular format), the other is about whether certain files exist in the tree. It's surprising to me that you think this connection is so obvious that you don't even need to explain it :-), whereas to me there is no strong connection at all. >> You wrote of the importance of "ChangeLog files" to forensics, but >> having that information in git commit messages is exactly equivalent >> (I use it for forensics all the time, in lots of projects). > >Once again, you take a part of the argument and try to analyze it >separately. > >The point was that if we start on the slippery slope of saying the >mistakes in the log messages are unimportant, we will eventually lose >both the information in the Git log records and the ability to produce >ChangeLog files. > >IOW, it's fortress -- if you dismantle one of its bastions, the others >will soon fall as well. The only way to avoid that is to hold all of >them. Okay, I understand your argument (I don't think your previous messages made it clear, but you've clarified it now). However, it just does not hold true in other projects. Why would we expect Emacs developers to be more slovenly than developers elsewhere? >> Do you see now why it at least looks like you're conflating these two different things? > >No. There are different aspects to this issue, and I described them >one after the other. Sometimes they are only loosely related, >sometimes they are more tightly coupled. This is the best way I could >express my thoughts. Since English is not the first language for >either of us, let's just agree that I failed to write in a style that >would allow you to better understand. English is my native language, by the way; I'm American, not German. FWIW, I couldn't tell from your writing that English is not your native language. >Once again, if there's a way to have the information in Git such that >a correct log could be generated from it, it would be fine with me, >and keeping the ChangeLog files in the repository won't be necessary, >as far as I'm concerned. But so far, keeping the files looks like the >cheapest way of satisfying all the requirements. I understand the >psychological effect of "going the old ways", but this is a practical >matter for me, not a religious one, and I'm looking for a practical >solution that would allow us to continue keeping an accurate accord of >the development history with as little overhead as possible. If the >best alternative is those "old ways", I have no problem with that. I think this project can successfully enforce ChangeLog-style entries in commit messages if we really want to, without much difficulty. There are a number of techniques for doing so, mostly social techniques, with a few technical helpers if we want. Other projects with similarly cohesive developer communities enforce such conventions all the time. I don't think it has anything to do with whether or not there are actual ChangeLog files in the repository; the fact that some of the people who don't want to keep those files are *also* people who don't want to use that style of entry generally, even in commit messages, is merely correlative -- getting rid of the files doesn't mean that everything else they advocate must happen too. I believe this is also what Paul was saying, though I don't want to put words in his mouth. Best regards, -Karl