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: Omitting Windows-specific parts from infrastructure changes Date: Thu, 22 Jan 2015 05:51:33 +0200 Message-ID: <83vbjzv5fe.fsf@gnu.org> References: <838uh32gpg.fsf@gnu.org> <54B9D960.1000001@cs.ucla.edu> <834mrp24b1.fsf@gnu.org> <54BBF6E7.3090802@cs.ucla.edu> <83a91gymld.fsf@gnu.org> <54BC08B2.8070302@cs.ucla.edu> <837fwjzx5f.fsf@gnu.org> <54BC18B9.50202@cs.ucla.edu> <83y4oyycz8.fsf@gnu.org> <54BD4657.3010202@cs.ucla.edu> <83egqqy637.fsf@gnu.org> <54BD81C4.1070109@cs.ucla.edu> <833875xvin.fsf@gnu.org> <54BEC86A.7060605@cs.ucla.edu> <83d268w2w9.fsf@gnu.org> <54BFE299.3060600@cs.ucla.edu> <833874vx1e.fsf@gnu.org> <54C00076.1020406@cs.ucla.edu> <831tmnx4e6.fsf@gnu.org> <87egqnhnae.fsf@fencepost.gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1421898728 28319 80.91.229.3 (22 Jan 2015 03:52:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 22 Jan 2015 03:52:08 +0000 (UTC) Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 22 04:52:07 2015 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 1YE8oQ-0004pA-PP for ged-emacs-devel@m.gmane.org; Thu, 22 Jan 2015 04:52:06 +0100 Original-Received: from localhost ([::1]:51069 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YE8oQ-0000LX-99 for ged-emacs-devel@m.gmane.org; Wed, 21 Jan 2015 22:52:06 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39396) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YE8oD-0000L7-1e for emacs-devel@gnu.org; Wed, 21 Jan 2015 22:51:54 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YE8oC-0007Rr-0v for emacs-devel@gnu.org; Wed, 21 Jan 2015 22:51:52 -0500 Original-Received: from mtaout27.012.net.il ([80.179.55.183]:37871) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YE8o6-0007QW-8M; Wed, 21 Jan 2015 22:51:46 -0500 Original-Received: from conversion-daemon.mtaout27.012.net.il by mtaout27.012.net.il (HyperSendmail v2007.08) id <0NIK00N007244H00@mtaout27.012.net.il>; Thu, 22 Jan 2015 05:44:39 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout27.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NIK00PE67QF9Q00@mtaout27.012.net.il>; Thu, 22 Jan 2015 05:44:39 +0200 (IST) In-reply-to: <87egqnhnae.fsf@fencepost.gnu.org> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.183 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:181549 Archived-At: > From: David Kastrup > Cc: Paul Eggert , emacs-devel@gnu.org > Date: Wed, 21 Jan 2015 21:49:29 +0100 > > Eli Zaretskii writes: > > >> Date: Wed, 21 Jan 2015 11:39:34 -0800 > >> From: Paul Eggert > > > >> This is starting to get ridiculous. Let's drop the discussion, as we're > >> not making any progress (quite the reverse, I'm afraid). > > > > I already suggested several ways to resolve this. Feel free to make > > your own suggestions, provided that the result will be that such > > changes are done everywhere, without unduly punishing your fellow > > developers who offer you help to do parts of your job. > > It's not his job. We are rather talking about how to enable different > people interested in different things to continue working on code in the > same Emacs repository. No, we are talking about making changes in infrastructure used by all platforms. Once someone decides to make such changes, making good-faith effort to do that in all parts of Emacs is part of the job. It could be done either by actually making those changes all over, or by asking platform maintainers to do the parts related to their platforms. In the latter case, the platform maintainers should have enough information about the proposed change to be able to do their parts without investing too much time and effort where the initiator can help them avoid that. For example, in the recently discussed changeset that uses CALLN for some C-level calls to Lisp APIs, the information that should be passed to platform maintainers is how to identify the offending calls. This information is clear to the person who initiated the change and it's possible to describe it in a sentence or two. I have hard time understanding how this kind of requirement could be described as impossible or hard to comply.