From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: next emacs version? Date: Mon, 22 Mar 2010 22:39:14 -0700 Message-ID: <3240B88E3FE54DACB354B0758A455492@us.oracle.com> References: <56D10E2523764AC98D99CEBC55DBAD93@us.oracle.com><83iq8sigyq.fsf@gnu.org><83d3z0i3nu.fsf@gnu.org><911BA1D06CEB4306924D0069BA2D3DFF@us.oracle.com><83bpeki18a.fsf@gnu.org><83aau4hv38.fsf@gnu.org><0E10B96B5C814EE8B95B57972F13E189@us.oracle.com><5E984B3C-4B86-4FA6-8675-4C8501CC2285@raeburn.org> <878w9jix51.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1269322903 13189 80.91.229.12 (23 Mar 2010 05:41:43 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 23 Mar 2010 05:41:43 +0000 (UTC) Cc: 'Ken Raeburn' , emacs-devel@gnu.org To: "'Stephen J. Turnbull'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 23 06:41:36 2010 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.69) (envelope-from ) id 1Ntwrk-000765-D8 for ged-emacs-devel@m.gmane.org; Tue, 23 Mar 2010 06:41:34 +0100 Original-Received: from localhost ([127.0.0.1]:44623 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ntwrb-0003NV-Op for ged-emacs-devel@m.gmane.org; Tue, 23 Mar 2010 01:41:15 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NtwrU-0003NQ-N9 for emacs-devel@gnu.org; Tue, 23 Mar 2010 01:41:08 -0400 Original-Received: from [140.186.70.92] (port=50591 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NtwrS-0003NI-TB for emacs-devel@gnu.org; Tue, 23 Mar 2010 01:41:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NtwrR-0005Yu-BN for emacs-devel@gnu.org; Tue, 23 Mar 2010 01:41:06 -0400 Original-Received: from rcsinet11.oracle.com ([148.87.113.123]:59236) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NtwrR-0005Yl-3k for emacs-devel@gnu.org; Tue, 23 Mar 2010 01:41:05 -0400 Original-Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet11.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o2N5ewGJ026048 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 23 Mar 2010 05:41:03 GMT Original-Received: from acsmt355.oracle.com (acsmt355.oracle.com [141.146.40.155]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o2LFjm0H014158; Tue, 23 Mar 2010 05:40:57 GMT Original-Received: from abhmt014.oracle.com by acsmt355.oracle.com with ESMTP id 102504831269322755; Mon, 22 Mar 2010 22:39:15 -0700 Original-Received: from dradamslap1 (/10.175.204.81) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 22 Mar 2010 22:39:14 -0700 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <878w9jix51.fsf@uwakimon.sk.tsukuba.ac.jp> Thread-Index: AcrKMZs6z8fI1V+vRFemukJPi5zKgQAGHEhA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Source-IP: acsmt355.oracle.com [141.146.40.155] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090207.4BA8546A.004B:SCFMA4539814,ss=1,fgs=0 X-detected-operating-system: by eggs.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:122532 Archived-At: >> This is a common occurrence/predicament. I (and I assume others >> too) sometimes get bug reports for my libraries that really amount >> to Emacs dev changes "breaking" things. Much of the time my answer >> must be "Too bad. I don't support ongoing Emacs development. Wait >> until the next Emacs release". > > What's the problem? That is the correct answer (modulo the addition > of "patches that work before and after the Emacs change welcome", if > appropriate for your development policy). There's no problem. That is exactly what I do. But as I mentioned, in some cases a minor change to my code can enable users to keep using it after some Emacs dev change. And so I sometimes make such a change to help them out, though still with no commitment to keep things synced and working wrt a moving dev target. IOW, I do this kind of update only exceptionally, and only if the change is minor and I expect that the dev code will be fairly stable wrt the change.