From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: VMS support Date: Sun, 27 Jul 2008 12:51:12 -0700 Message-ID: <200807271951.m6RJpC5s000478@sallyv1.ics.uci.edu> References: <87iquzmcxm.fsf@stupidchicken.com> <87d4l76ntu.fsf@ambire.localdomain> <8763qznhfd.fsf@stupidchicken.com> <87k5fcc2ui.fsf@ambire.localdomain> <873alz681f.fsf@ambire.localdomain> <200807241655.m6OGtiqp008494@sallyv1.ics.uci.edu> <200807271841.m6RIftSS024933@sallyv1.ics.uci.edu> <200807271906.m6RJ6VOw008253@sallyv1.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1217188815 4872 80.91.229.12 (27 Jul 2008 20:00:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 27 Jul 2008 20:00:15 +0000 (UTC) Cc: Thien-Thi Nguyen , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jul 27 22:01:04 2008 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 1KNCQM-0007vO-K0 for ged-emacs-devel@m.gmane.org; Sun, 27 Jul 2008 22:00:58 +0200 Original-Received: from localhost ([127.0.0.1]:58393 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KNCJs-00029U-4T for ged-emacs-devel@m.gmane.org; Sun, 27 Jul 2008 15:54:16 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KNCJn-00029J-5x for emacs-devel@gnu.org; Sun, 27 Jul 2008 15:54:11 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KNCJi-00028M-BT for emacs-devel@gnu.org; Sun, 27 Jul 2008 15:54:10 -0400 Original-Received: from [199.232.76.173] (port=38811 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KNCJi-00028H-7H for emacs-devel@gnu.org; Sun, 27 Jul 2008 15:54:06 -0400 Original-Received: from sallyv1.ics.uci.edu ([128.195.1.109]:59081) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1KNCJh-0007zL-Tu for emacs-devel@gnu.org; Sun, 27 Jul 2008 15:54:06 -0400 X-ICS-MailScanner-Watermark: 1217793073.33815@2Z2+VJy/eWP0LWaxsmmWbg Original-Received: from mothra.ics.uci.edu (mothra.ics.uci.edu [128.195.6.93]) by sallyv1.ics.uci.edu (8.13.7+Sun/8.13.7) with ESMTP id m6RJpC5s000478; Sun, 27 Jul 2008 12:51:13 -0700 (PDT) In-Reply-To: (Stefan Monnier's message of "Sun, 27 Jul 2008 15:31:18 -0400") Original-Lines: 27 X-ICS-MailScanner: Found to be clean X-ICS-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.44, required 5, autolearn=disabled, ALL_TRUSTED -1.44) X-ICS-MailScanner-From: dann@mothra.ics.uci.edu X-detected-kernel: by monty-python.gnu.org: Solaris 10 (beta) 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:101584 Archived-At: Stefan Monnier writes: > > If you only can spend a few minutes at a time when doing this (and > > I do), you can't write ChangeLogs when doing the work because they > > will conflict on updates. > > You should place the ChangeLog text somewhere where it won't conflict [snip] Yes there are solutions to all these, but they mean just more work, and mean changing the normal work style, which is equivalent to more work. > > On the other hand the gain is inexistent. > > If someone ever intends to pick up this code and do something useful > with it, having it cleanly delimited by before/after tags is > very helpful. If it's not commited as a single commit, you risk having > your change be interleaved with other unrelated changes. Of course, if > nobody ever picks it up, the gain is indeed inexistent, but the cost > really seems pretty minor compared to the effort needed to figure out > how to remove the code (which parts to remove, etc...). That's what I've been saying, its absolutely _not_ minor. And trading requiring to do work now for _maybe_ avoiding work in the future when _maybe_ someone _might_ pick up the code is a bad tradeoff. So the question is, will you continue this policy?