From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Removing MULTI_KBOARD Date: Sat, 23 Aug 2008 23:15:03 +0300 Message-ID: References: <200808011209.m71C9Tj3018356@sallyv1.ics.uci.edu> <200808020655.m726tvsI017108@sallyv1.ics.uci.edu> <200808020927.m729Rnov027876@sallyv1.ics.uci.edu> <489432B0.2000305@gnu.org> <87r697qzn3.fsf@stupidchicken.com> <18580.58502.366085.330994@kahikatea.snap.net.nz> <200808040115.m741Fp6T000371@sallyv1.ics.uci.edu> <200808231824.m7NIOcqI011373@sallyv1.ics.uci.edu> <200808231913.m7NJDQxZ002663@sallyv1.ics.uci.edu> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1219522517 26947 80.91.229.12 (23 Aug 2008 20:15:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 23 Aug 2008 20:15:17 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Dan Nicolaescu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Aug 23 22:16:10 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 1KWzWr-0004Ca-Uj for ged-emacs-devel@m.gmane.org; Sat, 23 Aug 2008 22:16:10 +0200 Original-Received: from localhost ([127.0.0.1]:59365 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KWzVu-00088s-6F for ged-emacs-devel@m.gmane.org; Sat, 23 Aug 2008 16:15:10 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KWzVq-00088b-Qt for emacs-devel@gnu.org; Sat, 23 Aug 2008 16:15:06 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KWzVp-00088C-Fb for emacs-devel@gnu.org; Sat, 23 Aug 2008 16:15:06 -0400 Original-Received: from [199.232.76.173] (port=54587 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KWzVp-000887-Ct for emacs-devel@gnu.org; Sat, 23 Aug 2008 16:15:05 -0400 Original-Received: from mtaout1.012.net.il ([84.95.2.1]:57492) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KWzVo-0003Z2-Tx for emacs-devel@gnu.org; Sat, 23 Aug 2008 16:15:05 -0400 Original-Received: from HOME-C4E4A596F7 ([84.229.211.50]) by i-mtaout1.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0K620064SLLZS510@i-mtaout1.012.net.il> for emacs-devel@gnu.org; Sat, 23 Aug 2008 23:15:35 +0300 (IDT) In-reply-to: <200808231913.m7NJDQxZ002663@sallyv1.ics.uci.edu> X-012-Sender: halo1@inter.net.il X-detected-kernel: by monty-python.gnu.org: Solaris 9.1 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:102889 Archived-At: > From: Dan Nicolaescu > Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org > Date: Sat, 23 Aug 2008 12:13:24 -0700 > > Eli Zaretskii writes: > > > > From: Dan Nicolaescu > > > Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org > > > Date: Sat, 23 Aug 2008 11:24:38 -0700 > > > > > > Was the removed MULTI_KBOARD code actually needed? > > > > I don't know. I debugged the current code, and never looked back, > > because I knew it was pointless, and because in my experience > > comparing with older versions is not an efficient way of debugging a > > program. It's all in the logs and in CVS, if you really want to know. > > So you are in effect saying that you preemptive attack was baseless and > without any technical justification (the HR approach was so wrong that's > not even worth disscussing). Refusing to provide a technical > justification after so many requests is quite telling. Thank you. Look, Dan, it's quite clear that you want to pick up this fight right where you left off. But I'm done fighting. The code and the logs are there for everyone to see and study, and they speak for themselves. They are the technical justification you are asking for, as far as I'm concerned. Whatever conclusions you draw from that is your own business and responsibility.