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:53:20 +0200 Message-ID: <83twzjv5cf.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> <87y4ovsxqj.fsf@fencepost.gnu.org> <83y4ovvoyv.fsf@gnu.org> <87a91bhmwf.fsf@fencepost.gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Trace: ger.gmane.org 1421898823 29957 80.91.229.3 (22 Jan 2015 03:53:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 22 Jan 2015 03:53:43 +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:53:43 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 1YE8py-0005iK-Ix for ged-emacs-devel@m.gmane.org; Thu, 22 Jan 2015 04:53:42 +0100 Original-Received: from localhost ([::1]:51072 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YE8px-00010n-TB for ged-emacs-devel@m.gmane.org; Wed, 21 Jan 2015 22:53:41 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39854) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YE8pl-00010f-Lb for emacs-devel@gnu.org; Wed, 21 Jan 2015 22:53:30 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YE8pk-0008GF-NM for emacs-devel@gnu.org; Wed, 21 Jan 2015 22:53:29 -0500 Original-Received: from mtaout26.012.net.il ([80.179.55.182]:46412) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YE8pf-0008Fo-Qs; Wed, 21 Jan 2015 22:53:24 -0500 Original-Received: from conversion-daemon.mtaout26.012.net.il by mtaout26.012.net.il (HyperSendmail v2007.08) id <0NIK00H007J6JZ00@mtaout26.012.net.il>; Thu, 22 Jan 2015 05:53:14 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout26.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NIK00AYO84QTW70@mtaout26.012.net.il>; Thu, 22 Jan 2015 05:53:14 +0200 (IST) In-reply-to: <87a91bhmwf.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.182 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:181550 Archived-At: > From: David Kastrup > Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org > Date: Wed, 21 Jan 2015 21:57:52 +0100 >=20 > Eli Zaretskii writes: >=20 > >> From: David Kastrup > >> Cc: Eli Zaretskii , emacs-devel@gnu.org > >> Date: Wed, 21 Jan 2015 21:08:20 +0100 > >>=20 > >> Emacs is developed with a distributed version control system so = working > >> on private changes is perfectly possible without affecting the c= ommon > >> public repository. > >>=20 > >> Where a change requires involving multiple platform maintainers,= it is > >> easily possible to first propose/provide the change in a branch = where > >> the respective platform developers able to test or cater for a c= hange > >> can prepare such changes without affecting the usability of the = master > >> branch for other developers. > > > > That's certainly a possibility. But it, too, assumes some minima= l > > level of cooperation between the platform maintainers. At the ve= ry > > least, the idea and perhaps also the details of the change should= be > > published. It makes no sense to ask others to guess how to find = which > > places on their platforms need change from large diffs. >=20 > I disagree here since those others will know the way around their > platform code better than someone catering for a different platform= . Once the information about what should be changed is given, yes. And that is all that was requested. > I would not myself go pointing out which stuff should be changed in= the > Windows code in order to parallel some GNU/Linux specific code chan= ges > I=A0submit. No one requested that. > But that does not mean that a contributor should refrain from descr= ibing > what he had to do on _his_ platform (with a high-level description > rather than one tied into the platform-specific code) to accommodat= e the > changes, and what functionality will likely be affected similarly o= n > other platforms. Exactly, this is the only request.