From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lars Ingebrigtsen Subject: Re: Sync up the org in emacs master to org maint branch? Date: Thu, 02 Feb 2017 13:10:07 +0100 Message-ID: References: <87k29d7zvw.fsf@engster.org> <87fuk08i01.fsf@engster.org> <87d1f36xnc.fsf@engster.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: (John Wiegley's message of "Wed, 01 Feb 2017 21:56:21 -0500") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sender: "Emacs-devel" To: David Engster Cc: Bastien Guerry , Emacs developers , Phillip Lord , emacs-org list , Kaushal Modi List-Id: emacs-orgmode.gnu.org John Wiegley writes: > In fact, what we're doing feels like if Python included Django in its main > repository, just to solve Django's problems of compatibility, testing, and > making its bugs known to the main Python developers. I guess that would be a fair comparison. If Django had traditionally always been distributed along with Python, and maintained in the Python repo, and the suggestion now would be to move Django to a part of the Python repo that very few developers look at, but Django would continue to be distributed with Python, and all Django bug reports would continue to go to the Python bug repository, and Python developers would continue to be responsible for QA and bug fixing of Django. See? It's totally the same thing. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no