From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Omitting Windows-specific parts from infrastructure changes Date: Wed, 21 Jan 2015 21:57:52 +0100 Message-ID: <87a91bhmwf.fsf@fencepost.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> 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 1421873890 2038 80.91.229.3 (21 Jan 2015 20:58:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 21 Jan 2015 20:58:10 +0000 (UTC) Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 21 21:58:09 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 1YE2Lo-0004I4-PO for ged-emacs-devel@m.gmane.org; Wed, 21 Jan 2015 21:58:08 +0100 Original-Received: from localhost ([::1]:50140 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YE2Lo-0002Cr-1c for ged-emacs-devel@m.gmane.org; Wed, 21 Jan 2015 15:58:08 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47453) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YE2La-0002CV-7v for emacs-devel@gnu.org; Wed, 21 Jan 2015 15:57:55 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YE2LZ-0003nU-7U for emacs-devel@gnu.org; Wed, 21 Jan 2015 15:57:54 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:37817) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YE2LZ-0003nC-4D for emacs-devel@gnu.org; Wed, 21 Jan 2015 15:57:53 -0500 Original-Received: from localhost ([127.0.0.1]:44992 helo=lola) by fencepost.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YE2LY-0007M0-JQ; Wed, 21 Jan 2015 15:57:52 -0500 Original-Received: by lola (Postfix, from userid 1000) id 0EF35E0468; Wed, 21 Jan 2015 21:57:52 +0100 (CET) In-Reply-To: <83y4ovvoyv.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 21 Jan 2015 22:49:28 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e 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:181533 Archived-At: Eli Zaretskii writes: >> 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 common >> 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 change >> 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 minimal > level of cooperation between the platform maintainers. At the very > 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. I disagree here since those others will know the way around their platform code better than someone catering for a different platform. 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 changes I=A0submit. But that does not mean that a contributor should refrain from describing what he had to do on _his_ platform (with a high-level description rather than one tied into the platform-specific code) to accommodate the changes, and what functionality will likely be affected similarly on other platforms. --=20 David Kastrup